Consumable holder with a cycle structure for an appliance

ABSTRACT

A consumable holder for use in an appliance configured to perform an operation cycle related to a consumable in the consumable holder, in response to a cycle structure, has or is enabled to acquire information about the cycle structure. The information about the cycle structure can be communicated to the appliance for use by the appliance to change the cycle structure and thereby change the operation cycle related to the consumable.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part of U.S. patent applicationSer. No. 11/932,876, filed Oct. 31, 2007, which is acontinuation-in-part of International Patent Application No.PCT/US2006/022503, filed Jun. 9, 2006, which further claims priority onU.S. Provisional Patent Application No. 60/595,148, filed Jun. 9, 2005.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to devices that hold consumables used by oroperated on by a communicating appliance.

2. Description of the Related Art

Household appliances typically operate on an article using one or morecycles of operation. Many appliances perform the cycles of operationusing a consumable. A consumable comprises a finite supply of at leastone product or a perishable good that must be periodically replenishedor replaced. For example, a washing machine might use a detergent and afabric softener while washing clothes, or a dishwasher might use adetergent and a water softener while washing dishes. In some cases,appliances perform cycles of operation on a consumable as the article. Aconsumable may be a food item where, for example, a range oven or amicrowave oven might perform a cycle of operation on the consumable.

In performing a cycle of operation, an appliance may also use aresource. A resource comprises a product or good that is in relativelyconstant and unlimited supply. Common resources include utilities, suchas water, electricity, air, or gas. Sometimes a consumable is mixed witha resource, as for example, when a detergent is mixed with water.

It is known to provide communication between an appliance and a devicethat affects use of a consumable by the appliance. However, there is aneed to improve communication between consumable holders and appliancesor between consumables and appliances.

SUMMARY OF THE INVENTION

According to the invention, a consumable holder for use in an applianceconfigured to perform an operation cycle related to a consumable in theconsumable holder, in response to a cycle structure, has or is enabledto acquire information about the cycle structure. The information aboutthe cycle structure can be communicated to the appliance for use by theappliance to change the cycle structure and thereby change the operationcycle related to the consumable.

The information about the cycle structure can be represented bykey-value pairs, XML, relational data tables, comma separated variablefiles, a hierarchical composite tree or graph, byte arrays, datapackets, command objects, binary encoded data, data encoded as aprogramming language such as a C header file, text, scripts, serializedobjects, or messages. In one aspect, the consumable holder can include asensor and the data is acquired from the sensor. In another aspect, thedata can be acquired from a distinct source of information about theconsumable or the consumable holder.

The information can include data about one or more attributes of theconsumable that would enable the appliance to ascertain the utility ofthe consumable. The information can be such things as a sound, agraphic, a ring tone, or licensable information. The information holdercan be a bag, a box, a carton, a bottle, a can, a cartridge, a bowl, adish, a plate, or any other rigid or semi-rigid body suitable to containa substance.

The information can be created by an authoring tool, which can reside ina user interface operably connected to the appliance.

In another aspect of the invention, a performance tag is defined foraffixing to a consumable holder for use in an appliance configured toperform an operation cycle related to a consumable in the consumableholder, or an article adapted to be operated on in an applianceconfigured to perform an operation cycle related to the article, theoperation cycle being in response to a cycle structure. The performancetag includes information about the cycle structure or other information.Whichever, the information about the cycle structure or the otherinformation can be communicated to the appliance for use by theappliance to change the cycle structure and thereby change the operationcycle related to the consumable or related to the article.

As with the consumable holder, the information about the cycle structurecan be represented by key-value pairs, XML, relational data tables,comma separated variable files, a hierarchical composite tree or graph,byte arrays, data packets, command objects, binary encoded data, dataencoded as a programming language such as a C header file, text,scripts, serialized objects, or messages. The other information caninclude a link to another source of information about the cyclestructure.

In another aspect of the invention, an article of the type to beoperated on in an appliance configured to perform an operation cyclerelated to the article in response to a cycle structure, includes aperformance tag having information about the cycle structure. Theinformation about the cycle structure can be communicated to theappliance by message for use by the appliance to change the cyclestructure and thereby change the operation cycle related to the article.

In another aspect of the invention, a consumable holder for use in anappliance configured to perform an operation cycle related to aconsumable in the consumable holder in response to a cycle structureincludes a performance tag having information about the cycle structure.The information about the cycle structure can be communicated to theappliance for use by the appliance to change the cycle structure andthereby change the operation cycle related to the consumable.

Preferably, the information includes data about appliance types, fabrictypes, or stain types so that the information can be used alone orcombined with the other information to create or modify a cycle ofoperation in response to the information.

In another aspect of the invention, a consumable information holder isprovided for use by an appliance configured to perform an operationcycle related to a consumable in response to a cycle structure. Theconsumable information holder includes information about the cyclestructure or about user interface data. The information about the cyclestructure or the user interface data can be communicated to theappliance for use by the appliance to change the cycle structure andthereby change the operation cycle related to the consumable or torender the user interface data.

The information about the cycle structure is represented by one ofkey-value pairs, XML, relational data tables, comma separated variablefiles, a hierarchical composite tree or graph, byte arrays, datapackets, command objects, binary encoded data, data encoded as aprogramming language such as a C header file, text, scripts, serializedobjects, or messages. The consumable information holder can be aconsumable holder, a performance tag, a consumable, or a data pod.

Preferably, the information includes data about an attribute of theconsumable that would enable the appliance to ascertain the utility ofthe consumable. The information includes such things as a sound, agraphic, a ring tone, licensable information, advertising information,usage instructions, purchasing and replenishment information, oringredient information relating to the consumable. The information caninclude any combination of first and second cycle structures and firstand second user interface data sets. Preferably, the first and secondcycle structures and the first and second user interface data sets areassociated, respectively, with first and second appliances or appliancetypes. The consumable information holder can be configured to receiveand store information associated with the consumable

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a schematic view of an appliance coupled to and comprising aconsumable holder according to the invention.

FIG. 2 is a schematic view of a consumable holder according to theinvention.

FIG. 3 is a schematic view of an operation cycle component for use witha communicating appliance.

FIG. 4 is a schematic view of an appliance controller with a cyclearchitecture.

FIG. 5 is a schematic diagram showing the communications controlling theoperation of an appliance.

FIG. 6 is a schematic view of a consumable and a consumable readeraccording to one embodiment of the invention for use with acommunicating appliance.

FIG. 7 is a schematic view of a remote user interface according to oneembodiment of the invention for use with a communicating appliance.

FIG. 8 is a schematic view of a network of appliances and clientsconnected on multiple networks by couplers.

FIG. 9 is a schematic view of a source of information about resourcesconnected to an appliance through two couplers.

FIG. 10 is a schematic diagram showing the transfer of an operationcycle accessory between two appliances.

FIG. 11 is a schematic diagram showing the operation of consumablereader with an appliance that is affected by information associated witha consumable.

FIG. 12 illustrates synchronous data collection by binding messages in acommand group.

FIG. 13 illustrates the technique of FIG. 11 to bind event messages.

FIG. 14 illustrates messaging between a consumable holder and anappliance according to one embodiment of the invention.

FIG. 15 illustrates messaging between a consumable holder and anappliance according to another embodiment of the invention.

FIG. 16 illustrates messaging between a consumable holder and anappliance according to another embodiment of the invention.

FIG. 17 is a schematic perspective view of a refrigeration appliancewith a water filter cartridge system embodying the principles of thepresent invention.

FIG. 18 is a perspective view of the water filter cartridge system ofFIG. 16 shown in isolation.

FIG. 19 is a perspective view of components of the water filtercartridge system of FIG. 17 with a cartridge being slightly withdrawnfrom a housing.

FIG. 20 is a flow chart illustrating an exemplary water filter cartridgereplacement process according to one embodiment of the invention.

FIG. 21 is a schematic diagram of an example of the creation of a cyclestructure for an appliance by way of a consumable holder according tothe invention.

FIG. 22 is a flow chart illustrating the steps implementing a scriptaccording to the invention.

FIG. 23 schematically illustrates a taxonomy control using a taxonomydataset in combination with the software architecture to control theoperation of one or more components within the appliance without directknowledge of the functions for the component.

FIG. 24 schematically illustrates one embodiment of a taxonomyarchitecture according to the invention.

FIG. 25 schematically illustrates a second embodiment of a taxonomyarchitecture according to the invention.

FIG. 26 is a modified version of the software architecture of FIG. 23for another operating environment.

FIG. 26A is a detailed portion of the taxonomy engine of FIG. 26.

FIG. 27 schematically illustrates a method utilizing the taxonomyarchitecture according to the invention.

FIG. 28 illustrates an exemplary data structure used in the taxonomyarchitecture of the invention.

FIG. 29 illustrates a second exemplary data structure used in thetaxonomy architecture of the invention.

FIG. 30 is a schematic illustration of a pair of software operatingenvironments, each corresponding to a different component with its ownSA, and connected by the internal communications network.

FIG. 31 is a schematic view of a network of appliances and clientsconnected on multiple networks by couplers.

FIG. 32 is a schematic view of a process of creating main structures ofan embedded virtual router.

FIG. 33 is a schematic view of a plurality of hardware components thatare communicatively connected using chaining.

FIG. 34 is a schematic view of relationship between structuralcomponents within an appliance control system.

DESCRIPTION OF THE INVENTION

Appliances and Consumables

Looking first at FIG. 1, an embodiment of the invention comprises anappliance 12 having a process control apparatus 14 and a consumableholder 16. The appliance 12 is configured to perform an operation on aphysical article, such as clothing or food, using a resource such aswater, temperature-controlled air (hot or cold), steam, gas,electricity, and the like. The process control apparatus 14 isconfigured to implement and control a cycle comprising at least oneoperation. The process control apparatus 14 can comprise one or morecomponents, such as electronic control boards, wiring and wiringharnesses, power-supplies, sensors integrated with the electronics asdigital or analog inputs, and actuators like valves, relays, heaters,and the like, any or all of which can integrate with the electronics asdigital or analog outputs. Examples of appliances 12 that perform anoperation on a physical article include a wide range of device types,including but not limited to, washers, dryers, ovens, ranges, steamcookers, ice makers, refrigerators, drink makers and the like. Articlesare the objects upon which a user intends the appliance to perform itscycle of operation. Typical examples as mentioned above would includefood and clothing.

The consumable holder 16 is configured to hold, carry, supply,communicate with, or otherwise interact directly with a consumable 24.When performing a cycle of operation on an article, the appliance 12will often use at least one consumable 24. A consumable 24 in one sensecomprises a substance, device, or other product that would be at leastpartially consumed or transformed by an appliance during a cycle ofoperation on an article, such that the consumable must be periodicallyreplaced or replenished. The period after which the consumable must bereplaced or replenished can be but is not limited to a single cycle ofoperation, multiple cycles of operation, an amount of time, or a numberof uses. For example, many common washing machines require that a userplace a single dose of detergent in a dispenser prior to initiating acycle of operation. For each subsequent cycle of operation, the usermust again place a single dose in the dispenser, as a single dose ofdetergent is consumed by the washing machine during each cycle ofoperation.

In some cases, the consumable can be the article on which the appliance12 performs the cycle of operation, and the consumable can besubsequently consumed by a user. Thus, a consumable 24 also includesanything that would be consumed or otherwise used by a person, such asfood, beverages, cosmetics, or medicine. For example, in a cooking orrefrigeration appliance, the consumable can be a food item, and thecycle of operation comprises heating or cooling the food.

Consumables are to be distinguished from resources, although resourcesmay in some circumstances be “consumed” during a cycle of operation.Resources are fluid or gas commodities that are continuously availableto an appliance, and used by the appliance in its cycles of operation onarticles. Typical examples as mentioned above would include water andair. In some cases, a resource may also be considered an article as in arefrigerator that chills and dispenses water. Water in that instance isa resource (continuously available to the refrigerator), but also anarticle (intended by the user for the refrigerator to act upon). Thecycles of operation would include the chilling and dispensing. Thingsthat hold or supply resources such as water supply lines or air conduitsare not considered consumable holders 16. They would be “resourceholders”, which can be supplied by resource providers. In arefrigerator, for example, water supplied to the appliance 12 would beconsidered a resource and/or an article. If flavoring is mixed with thewater supplied to the appliance 12, the flavoring can be considered aconsumable 24, and whatever holds/supplies the flavoring to be theconsumable holder 16.

Consumables are also to be distinguished from parts in an appliance,although parts wear out and need to be replaced or replenished as doconsumables. Parts are devices, without which a cycle of operation bythe appliance or a principal function of the appliance would behampered. Examples include valves, actuators, switches, tubes, lamps,wiring, motors, pumps, seals, gears and the like. Consumables, one theother hand, are not critical to the operation of the appliance, althoughthey provide huge benefits to a user of the appliance. An appliance cantypically still operate on an article in some fashion without aconsumable.

Other examples further illustrate the foregoing distinctions. Considerusing an oven to cook a turkey in a roasting pan where there is a steamdispenser with a basting cartridge for automatic basting. The turkey isthe article upon which the appliance (the oven) performs its cycle ofoperation (cooking). But the turkey is also a consumable in the sensethat it is a food item to be consumed by the user. The basting cartridgewould be a consumable holder and its contents a consumable. The waterused to generate the steam is a resource, making the steam a changedresource. The roasting pan would be a second consumable holder, holdingthe turkey. In accord with the invention, the appliance or the roastingpan or some other device (such as a performance tag described below)might also hold information about the turkey or how to cook a turkey orhow to cook a turkey in different kinds of ovens. Such information wouldbe considered information about a consumable and information about acycle structure.

Consider also a powdered detergent box with a performance tag configuredto communicate with an appliance contemporaneously with the dispensingof the detergent to a washer. The washer is the appliance, the detergentis a consumable, and the box is a consumable holder. The performance tagcan hold information about the chemistry of the powder, informationabout cycle structures, and data about cycle structures wherein theinformation and data are associated with other information comprisingappliance types, fabric types, stain types, and the like so that thedata and information can be used alone or combined with the otherinformation to create a cycle of operation in response to the data andthe information and the other information and in response to the userand the user preferences about the cycle of operation, the data, theinformation, and the other information.

Consider also a detergent pellet with an etched or embossed or imprintedcycle structure enabled to communicate with an appliancecontemporaneously with being introduced into a washing machine before orduring a wash cycle. Here, the washing machine is an appliance and thedetergent pellet is a consumable. There is no separate consumableholder. The cycle structure is intended to effect the cycle of operation(washing). Consider also a detergent pellet having a data pod. Thedetergent pellet is a consumable, but the data pod is a form ofperformance tag that could communicate with an appliancecontemporaneously with being introduced into the use environment for thepurpose of effecting the cycle of operation.

In accord with the invention, a consumable or a consumable holder or aperformance tag or data pod or anything that can hold and conveyinformation (consumable information holder) might comprise one or morecycle structures. A first cycle structure can be associated with a firstappliance or first appliance type and a second cycle structure can beassociated with a second appliance or a second appliance type such thatthe appropriate cycle structures are introduced to the appropriateappliance or appliance type when the consumable or consumable holder isin useful communication with the appliances. For example, a frozen food(a consumable) or a package of frozen food (a consumable holder) mighthave cycle instructions for freezing, defrosting, or preserving cyclesin a refrigerator or freezer appliance, and also might have cycleinstructions for defrosting, cooking, or warming cycles for a cookingappliance like an oven or microwave.

A consumable information holder can comprise one or more user interfacedata sets, with or without cycle structures, which can be communicatedto a user interface, such as might be on the appliance. User interfacedata is considered to include anything that can be rendered to beresponsive to a user's senses, such a visual displays, audible sounds,and tactile displays. A first user interface data set can be associatedwith a first appliance or first appliance type and a second userinterface data set can be associated with a second appliance or a secondappliance type such that the appropriate user interface data areconveyed to a user interface associated with the appropriate applianceor appliance type when the consumable or consumable holder is in usefulcommunication with the appliances. For example, a frozen food (aconsumable) or a package of frozen food (a consumable holder) mightconvey to a refrigerator an expiration date to be rendered on a userinterface on the refrigerator. The frozen food or its package might alsoconvey to an oven serving suggestions to be rendered on a user interfaceon the oven.

Consumables, consumable holders, performance tags, data pods and thelike (consumable information holders) can be enabled not only to providedata, but also can be configured to receive and store informationassociated with the consumable in accord with the invention. Exemplaryinformation includes data about a consumable, a cycle structure, dataabout a cycle structure, tracking the number of times a shirt or a dishis washed, the number of cycles and the parameters thereof which havebeen executed by or in combination with an appliance and consumableholder, the types of consumables introduced into the use environment,information entered into an appliance user interface including cycleselections, usage patterns, user information, user identification, otherdata associated with the cycle of operation of an appliance, and anydata held by a datasource in communication with the holder, tag, or podwhich either the datasource writes to the holder, tag, or pod or anydata or the holder, tag, and pod reads from the datasource. Suchinformation can be sequentially added to a database on the consumableinformation holder for later retrieval. For example, a shirt with aperformance tag can keep data about how many times it has been washed,about different wash cycles it has been through, and the specificmachines it has been washed in.

More specific examples of consumables 24 for use with/by appliances 12include dispensing additives for laundry washers, dryers, or combinationwasher/dryer appliances. The additives can include, but are not limitedto, normal detergents, gentle detergents, dark clothing detergents, coldwater detergents, fabric softeners, chlorine bleaches, color-safebleaches, and fabric enhancement chemistry. Non-limiting examples offabric enhancers are additives to provide stain resistance, wrinkleresistance, water repellency, insect repellency, color fastness,fragrances, and anti-microbials.

An additive dispenser in this case would be a consumable holder 16 andcan be a single load dispenser that dispenses all of additive containedtherein during a single cycle or a bulk dispenser that dispenses onlysome of the additive contained therein during a single cycle. Anappliance comprising a bulk dispenser can meter and dispense the correctamount of additive for each particular load and provide information tothe user regarding the remaining amount of additive in the bulkdispenser after dispensing.

Because each additive can have different parameters associated with itsuse, information about each consumable can be provided with eachconsumable 24. This information can be provided on the packaging of theconsumable 24 (the consumable holder), in the consumable 24, or by anyother suitable means (performance tag, data pod, user interface, etc.).For example, different additives can have different concentrations, andthe amount of a given additive needed for a particular load will varydepending on the concentration of that additive. The amount of aparticular additive needed to complete a cycle of operation will alsodepend on the amount and type of laundry being treated, as well as thecondition of the laundry (e.g. soil and stain level). The amount, type,and condition of the laundry can be determined utilizing informationsupplied by the user, information gathered by sensors associated withthe appliance, or information otherwise obtained during the operation ofthe appliance 12.

Additional information provided with the consumable can also be used totailor the cycle of operation to that consumable 24. In a laundryapplication, the additive will have to be dispensed at the right timeduring the cycle, such as before, during, or after wash, rinse, spin, ordrying. Particular additives can also require that they are dispensedunder certain conditions, such as at a given water temperature or airtemperature. Additionally, particular additives might require at leastone additional step in a cycle for optimal performance. For example, thepresence of a particular additive might require that the cycle structurebe augmented by inserting an additional ordered collection of steps suchas filling at a new temperatures to a new level after spinning, thensoaking for an amount of time, then draining, then spinning for a newamount of time at a new spin speed between the original step in thecycle and the last step in the cycle.

The appliance process control apparatus 14 or the consumable holder 16can determine parameters to be used for the cycle of operation or thestructure of the appropriate cycle of operation or changes to anexisting cycle of operation for different operations based on theinformation provided with the consumable 24, user input, and informationobtained by sensors associated with the appliance 12. Exemplary typesand sources of information are found in the following table:

Information Information Information provided from the provided byprovided by consumable or consumable holder the user appliance sensorsNew Order Collection of Cycle Steps, Fabric Soil level Actions for EachSteps, a plurality of type Transition Logic expressions for each step,and the relationships between steps, actions, and logic expressions.Additive type Desired Load weight cycle When in cycle to dispense Fabrictype Load absorption Any special cycle parameters Load size Additiveremaining in dispenser Amount to dispense for a standard Fabric Soillevel load condition (soil level, stains, etc.) Special dispensermaintenance Dispensing considerations compartment used

Another example of consumables contemplated by the invention includesfilters used by an appliance 12. Refrigerators, dryers, washers, anddishwashers are all known to use filters that are consumed in the sensethat they must be replaced after a certain amount of time or usage dueto wear and dirtying of the filter. Filters, in particular, depending onthe embodiment may be construed as a consumable, a consumable holder, orboth. For example, if there is a filter assembly holding a filteringmaterial, then the filter assembly may be considered a consumable holderand the filtering material can be considered a consumable because it isdisposed of after it usability is consumed; its life and the life of theconsumable holder are significantly different. On the other hand, thefilter assembly and the filter material can be integrally formed andintroduced and removed from the use environment as a unit. In this case,the assembly and the filter material would be considered both aconsumable holder and consumable because the assembly and the filtermaterial comprise functionality and attributes of both consumableholders and consumables.

Consumables can also include food, as mentioned above, and articles ofclothing. Such consumables may or may not be contained by a consumableholder. However, non-contained consumables can still have consumableholder functionality in that they can comprise information about theconsumable that is retrievable by the appliance. For example, a fooditem can carry information about itself that is contained in edible inkprinted on the surface of the food item.

The appliance 12, the consumable holder 16, or both comprise at leastone interface 18 to couple the appliance and the consumable holder toeach other. The interface 18 can be an internal or external interfaceand can be configured to receive, connect to, or otherwise couple theconsumable holder 16 and the appliance 12. One or more interfaces 20 cancouple the appliance 12 and/or the consumable holder 16 to an externalsource or device, such as a power source, a consumable source and/or aconsumable reader. Either interface 18, 20 can comprise any number ofcoupling points, such as coupling points 18A-18F and 20A-20C for variouspurposes.

The coupling points in an interface 18, 20 can be configured forcoupling to a consumable holder 16, an appliance 12, a component thatcan facilitate engagement or interaction with a consumable holder 16, orany other source or device to be used with the appliance 12 and/orconsumable holder 16. For example, a coupling point 20C can beconfigured for connection to a consumable reader 22. Alternatively, theconsumable reader 22 can be incorporated into the appliance 12, and asensor can be connected to the appliance 12 and/or the consumable reader22 via a coupling point 20C. Further, a coupling point 20A can couplethe consumable holder 16 to a bulk source 26 of a consumable 24, such asa large bottle of detergent. A coupling point 20B can also couple anexternal power source 23 to the appliance 12 or to the consumable holder16.

Preferably, the appliance 12 and the process control apparatus 14include software architecture 1018 enabling the appliance to discover aconsumable holder 16 using network messages. For this purpose, theprocess control apparatus 14 can comprise at least one functionalidentifier and can send or receive messages to for the discovery offunctionalities, as discussed later. Likewise, the consumable holder 16can also comprise an instance of the software architecture 1018 and/oran SA Driver 1016, which will be discussed in more detail hereinafterwith respect to FIG. 8.

Consumable Holder

The consumable holder 16 comprises a device that holds or contains aconsumable 24. Typically the consumable 24 is contained by a receptacleof some sort, such as a container, a dispenser, a cartridge, a dish, abag, a carton, a conduit, or the like. In some cases, consumable holders16 can be nested within other consumable holders 16. For example, acartridge holding a consumable can be disposed in a dispenser, which isanother consumable holder 16.

In some cases articles on which the appliance operates—such as clothes,dishes, and food stuffs—may not be contained by receptacles and may notbe consumables or consumable holders in the sense herein defined, butrather articles enabled to perform at least some of the inventivefunctionalities of a consumable 24 and/or consumable holder 16. Anexample of an article with consumable holder 16 capabilities is a shirthaving a bar code thereon containing information that is directlyreadable by an appliance 12. The bar code can be, for example, on aperformance tag. The appliance 12 can use data and/or informationrepresented by the bar code for use in configuring and selecting thecycle of operation of the appliance. The bar code can be read by theappliance 12 while the shirt is being operated on contemporaneous withthe cycle of operation.

A performance tag is an information holder either integrally formed orselectively attached to an article and adapted to maintain its integrityover the life of the article. For example, a performance tag forclothing would be adapted to maintain its integrity throughout therepeated processes of washing in a washing machine appliance, drying ina dryer, being cleaned at a dry cleaners, being ironed, being left inthe sun, and being subjected to the impacts sustained during usage.Examples of impacts during usage for a shirt might occur during a soccermatch where the shirt impacts the earth and other players atconsiderable speeds and forces repeatedly. Likewise, performance tagsfor dishes would be subjected to similar impacts, and similar wash anddry cycles from a dishwasher. Performance tags integrally formed withfabric items might be sewn in, glued in, woven in, stamped on, orprinted on during the manufacturing of the article or by a home machineadapted to integrate the article and the tag. Performance tagsintegrally formed with dishware might be glued, stamped, printed,embossed, cast, molded, or otherwise formed during the manufacturing ofthe article or by a home machine adapted to integrate the article andthe tag. Performance tags that are selectively attached to an articlecould be attached by sewing, gluing, pining, sticking, printing,embossing, or other like methods in the home environment for articlesnot specifically adapted for receiving a performance tag. Performancetags are constructed of any suitable material which can be used to holdencoded information about a cycle structure, a cycle structure, orinformation about a consumable, the description of which is containedherein. Examples of materials for holding the information includemagnetic strips, bar codes, and images of encoded data including colorpatterns, shape patterns, plain texts, numeric identifiers, and thelike. An appliance having a cycle architecture and being incommunication with a performance tag (as for example by using aconsumable reader) can optimize the cycle of operation in the appliancefor the article in response to the cycle structure, data about a cyclestructure, and/or data about a consumable held by the performance tag.Performance tags can either hold information or hold other informationabout how to find the information. An example of a performance tag thatholds other information is a performance tag holding a URL wherein thedata returned when invoking the URL is the information. Further, theappliance can alter or optimize the user experience further by providinginformation on a user interface in response to the cycle structure, dataabout a cycle structure, and/or data about a consumable.

A consumable holder 16 can be integral with the appliance 12, as forexample, installed during manufacture and sold with the appliance, or itcan be made and sold separately as an upgrade or addition. It can bedisposed inside or outside or on the appliance. The interface 18 cancomprise at least one coupling point to couple the consumable holder 16to the appliance 12, and the interface 20 can comprise at least onecoupling point to couple the appliance 12 to an external resource ordevice, or couple the consumable holder 16 to an external resource ordevice. A coupling can be a physical coupling or a coupling can be anelectrical or wireless coupling. For example, a coupling 20 can comprisea scanner and an image to be scanned, such as a barcode. Any couplingpoint in the interface 18 can be configured such that the consumableholder 16 can be selectively or permanently coupled to the appliance 12.Coupling points can also be used to couple electronics in a consumableholder to a device such as a sensor or actuator, or to coupleelectronics in an appliance to a device such as a sensor or actuator. Incertain embodiments, electronics in a consumable holder can directlycouple the appliance to a device such as a sensor or actuator with theuse of a coupling point.

Referring now also to FIG. 2, the consumable holder 16 can be in theappliance as in FIG. 1, or separate from the appliance as contemplatedin FIG. 2. Either way, the consumable holder 16 can be connected to theappliance 12 by at least one interface 18 comprising a plurality ofcoupling points 18A-F. The interface 18 is configured to communicativelycouple the consumable holder 16 to the process control apparatus 14 ofthe appliance 12. Each coupling point can enable a different function.For example, a resource coupling point 18A can facilitate transmissionof the resource to a consumable holder 16, a resource coupling point 18Bcan facilitate transmission of the resource back to the appliance 12, adata coupling point 18C can facilitate data exchange between theappliance 12 and a consumable holder 16, a consumable coupling point 18Dcan facilitate transmission of a consumable 24 to the appliance 12, anda circuit coupling point 18E can couple a circuit to a consumable holder16 to trigger an actuator in the consumable holder 16 or in theappliance 12. Resource and consumable transmission between theconsumable holder 16 and the appliance 12 will normally require aphysical coupling. Data exchange and circuit coupling can requireelectrical connections, wireless connections, or optical couplingpoints. In another embodiment, a coupling point 18E can facilitatetransmission of a changed resource from the consumable holder 16 to theappliance 12. A changed resource may be one whose properties have beenchanged by a chemical, thermal, electrical, or other type of process.For example a changed resource may be one that has been heated, cleaned,cooled, mixed with a consumable, or generally treated in such a way thatit has at least one property with a different value.

The interface 18 can also include a power coupling point 18F. Thecoupling point 18F can deliver power to a consumable holder 16 or it candeliver power to the process control apparatus 14. Coupling point 18Fcan comprise a power connection adapted to transmit power to aconsumable holder 16. The power can be conventional AC at 110 V, DC at12 V, or even less, such as the power that is transmitted by a USBconnection. In some cases, the data coupling point 18C or the circuitcoupling point 18E can also function as a power source.

Continuing with FIG. 2, the consumable holder 16 has an internal source26′ and/or an external source 26″ of a consumable 24, such as areservoir, bottle, conduit, dispenser or bulk dispenser, cartridge,another appliance, another consumable holder, or a connection to adispenser. The consumable holder 16 can also have its own holder processcontrol apparatus 28 to control the dispensing or transmission of aconsumable 24 from the source 26, 26′, or 26″.

As discussed previously, the consumable holder 16 comprises resourcecoupling points 18A, 18B (which can be assimilated into a singlecoupling point) configured to exchange a resource with the appliance 12.The appliance 12 is configured to use the consumable 24 and the resourceto perform a physical operation on an article. The consumable holder 16may further comprise electronics 30 configured for communication withthe appliance process control apparatus 14. The electronics 30 canaffect a resource by communicating with the appliance process controlapparatus 14 when the consumable holder 16 is coupled to an appliance12. The electronics 30 can be configured to deliver a cycle of operationto the appliance 12. Alternatively, the electronics 30 can communicatewith the software architecture 1018 for the purposes of observing thecycle of operation and modifying the cycle of operation. The electronics30 may observe the cycle of operation using any of the data collectionschemes (as disclosed in the incorporated WO2006135726) supported by thesoftware architecture 1018. These data collection schemes include butare not limited to requesting data from the software architecture 34,receiving unsolicited events from the cycle of operation 1018, or bycreating new events that can be received by communicating with asoftware architecture having a DAQ (as disclosed in the incorporatedWO2006135726) and specifying the events to the DAQ for creation by theDAQ. In addition, the electronics 30 may alter the cycle of operation inresponse to the observations. In a first embodiment, the electronics 30can alter the cycle of operation by requesting to the softwarearchitecture 1018 that the appliance process control apparatus 14 enteran alternate operating mode enabling the electronics 30 to directlycontrol, partially or wholly, the cycle of operation. In a secondembodiment, the electronics can alter the cycle of operation by makingspecific requests to the software architecture 1018. In a thirdembodiment, the electronics can selectively alter the cycle structure 71using any of the techniques described herein (see descriptions of FIG. 5and FIG. 11) The electronics 30 can include a controller 32 and softwarearchitecture 1018 similar to that of the appliance 12 and/or a softwarearchitecture driver 1016. The electronics 30 can be powered by theconsumable holder 16 or via connection to the appliance 12. Theelectronics 30 can further comprise a client 40. Client 40 can comprisea plurality of arbitrary software components, the software architecturedriver 1016, an instance of the software architecture 1018, a converteras shown in FIG. 21, and any other software and data storage and dataaccess functionality.

The consumable holder 16 can also have a consumable reader 36, similarto the aforementioned consumable reader 22, coupled to the consumableholder 16 by external coupling point 20C. In this case, the consumablereader 36 is communicatively coupled to the controller 32 and to thesoftware architecture 1018. This enables information about theconsumable 24 and/or about the consumable holder 16 to be read from asource of information and transferred into the memory of the controller32 or into the memory at least one control board within the processcontrol apparatus 14 wherein the transferring is preferably accomplishedusing software architecture 1018.

The consumable holder 16 can further comprise at least one couplingpoint 20D configured to couple with at least one other correspondingcoupling point for resource/consumable transmission. Thus, couplingpoints can exchange or convey a resource, data, and/or a consumable 24to an appliance 12 or to another external device. A coupling point canconnect to a source of information about the consumable 24 and/or to aconsumable reader 22, 36 and/or to a resource separate from theappliance 12.

The consumable holder 16 can have at least one sensor 38 to sense one ormore attributes of a consumable 24 and/or its source 26. Attributes caninclude such things as amount, brand, type, composition, structuralform, expiration date, dispensing properties, nutritional information,temperature, pressure, and concentration. To store and inventory suchdata, the consumable holder 16 can utilize the controller 32. Suchinformation or data can also be conveyed to and/or presented at a userinterface in the consumable holder 16 or the appliance 12.

The holder process control apparatus 28 of the consumable holder 16 canbe configured to detect functionalities of the appliance 12, modifyfunctionalities of the appliance 12, be controlled by the appliance 12,or otherwise exchange data with the appliance process control apparatus14 of the appliance 12. The holder process control apparatus 28 can beused to actuate the transmission, dispensing, supplying, or usage of atleast one consumable 24 by actuating a mechanical part, such as a valve,conduit, solenoid, sensor, actuator, spring, transmission, motor, orgear. Additionally, the holder process control apparatus 28 can beconfigured to modify properties of one or more consumables or resourcessuch as temperature or a chemical property. For example, temperaturecould be raised by actuating a heater, and chemical properties might bechanged by controlling a mixture of at least two consumables and/orresources by using a motor and an auger. Additional auxiliaryfunctionalities not directly related to the actuation of consumables 24can be enabled by the holder process control apparatus 28. The holderprocess control apparatus 28 can optionally include a mechanism toeffect the use of a resource, such as an actuator for a valve.

The consumable holder 16 can receive resources from the appliance 12,act on the resources, and return the modified resources to theappliance. For example, in a washing machine or dishwasher, theconsumable holder 16 can receive water from the appliance 12 and returnthat water to the appliance 12 as grey water or as water mixed withdetergent. In this instance, detergent would be a consumable 24. Theconsumable holder 16 can thus export modified consumables 24 which haveeither been operated on by the consumable holder 16 or that have beenoperated on by the introduction of at least one resource. The consumableholder 16 can also dispense the consumable 24 directly to the appliance12.

The client 40 in the electronics 30 can contain a data set linking themodel of the appliance 12 or some other functional identifier such as aclass id, or an API ID, type, and/or version to the plurality ofconsumables 24 that the consumable holder 16 can contain. The data setcan further link any of these attributes to a plurality of cycles ofoperation for the appliance 12. The data set can also link cyclemodification or cycle operation data or cycle structure data or data forresponse to a query message to various combinations of appliances 12,consumables 24, and selected cycles. The data set can alternatively bein the appliance 12. The data in the data set can be modified by anetwork message sent by a node on the network, such as the consumableholder 16, the consumable 24, or the consumable reader 22, 36.

Software Architecture

The software architecture 1018 enables the consumable holder 16 todiscover one or more functionalities of the appliance 12 via messaging.The software architecture 1018 can also enable the consumable holder 16to respond to discovery messages so that the appliance 12 can discoverone or more functionalities of the consumable holder 16 or at least onecharacteristic of a consumable 24. The software architecture 1018 can belocated in the controller 32, hard-wired into the electronics 30,located in a client 40, or accessed separately. The process controlapparatus 28 can have at least one functional identifier known by thecontroller 32 and/or software architecture 1018, enabling the softwarearchitecture 1018 to respond to discovery messages with a response thatcontains data about the consumable holder process control apparatus 28.Generally, a consumable holder with a controller 32 and softwarearchitecture 1018 can initiate or respond to a plurality of discoverymessages either to find or disclose information to a node on a networkabout a component associated therewith or the appliance.

By employing a software architecture 1018 that enables facilecommunication between internal components of an appliance and between anexternal component and one or more of the internal components of theappliance, various components and accessories, including a consumableholder according to the invention, can communicate with the appliance toexpand the capability, functionality, and usability of the appliance,and particularly, an appliance that uses a consumable product during itsoperation, or otherwise operates on a consumable product. The appliancecan be any suitable appliance, such as a household appliance. Examplesof household appliances include, but are not limited to, clothes washingmachines, clothes dryers, ovens, dishwashers, refrigerators, freezers,microwave ovens, trash compactors, and countertop appliances, such aswaffle makers, toasters, blenders, mixers, food processors, coffeemakers, air purifiers and dehumidifiers, hot water heaters, watersoftners, blenders, and the like.

The appliance can be configured to perform a cycle of operation tocomplete a physical domestic operation on an article. Examples of thephysical domestic operations include a food preparation operation, afood preservation operation, a fluid treatment operation, a cleaningoperation, a personal care operation, a fabric treatment operation, anair treatment operation, and a hard surface treatment operation. The airtreatment operation can comprise, for example, air purification, airhumidification, air dehumidification, air heating, and air cooling. Thefood preparation operation can comprise, for example, food cleaning,food chopping, food mixing, food heating, food peeling, and foodcooling. The food preservation operation can comprise, for example, foodcooling, food freezing, and food storage in a specialized atmosphere.The fluid treatment operation can comprise, for example, fluid heating,fluid boiling, fluid cooling, fluid freezing, fluid mixing, fluidwhipping, fluid dispensing, fluid filtering, and fluid separation. Thecleaning operation can comprise, for example, dishwashing, fabricwashing, fabric treatment, fabric drying, hard surface cleaning, hardsurface treatment, hard surface drying, carpet cleaning, carpettreatment, and carpet drying. The personal care operation can comprise,for example, hair treatment, nail treatment, body massaging, teethcleaning, body cleaning, and shaving.

The internal components of the appliances can include any component thatparticipates in the operation of the appliance. Some of the internalcomponents have a corresponding controller (main controller, motorcontroller, user interface, etc.), which can be a simple microprocessormounted on a printed circuit board, and other components that have nocontroller. The components can comprise one or more devices that arecontrolled by the controller. Typically, the controller components incooperation, either directly or indirectly, through other components,control the operation of all of the components and the associateddevices to implement an operation or cycle for the appliance.

The software architecture can be implemented on and communicated over aninternal communications network on the appliance. The internalcommunications network connects the various internal components of theappliance and can be considered a closed network. One example of theinternal communications network used within the appliance is the WIDEnetwork protocol, created by Whirlpool, Inc., the assignee of thepresent patent application. The internal communications network must atleast address the physical layer of the OSI layered network model.Preferably, the internal communications network comprises allappropriate layers of the OSI model. The WIDE network protocol addressesthe physical layer and at least some aspects of the Link and Transportlayers.

The software architecture expands the communication ability of theappliance by adding upper layer functionalities to the network stackeffectively creating a fully functional appliance network incorporatingthe necessary aspects of the OSI layered network model likefragmentation and message reliability and session management, certainobject oriented functionalities like message routing using functionalidentifiers, discovery, and the like, and certain advanced routingfeatures like message propagation across multiple networks wheredistributed routing tables are used to facilitate the messagepropagation across the multiple networks and certain other importantfunctionalities like message binding, authentication of nodes, andmessage firewalls hereinafter referred to as “network.” Within theappliance, the software architecture can, but does not have to, resideon each of the components that have a controller. Those components withthe software architecture form a network node that can communicate withthe other nodes. In other words a network as it relates to thisinvention is any system of collaboration between arbitrary softwarecomponents, whether physical (shown for example in FIG. 8) or virtual(shown for example in FIG. 30).

The software architecture 1018 can perform multiple functions. Forexample, one function can relate to identifying each of the componentscorresponding to a node on the network, while another function canrelate to identifying capabilities or functions of the identifiedcomponents on the network. Yet another exemplary function is to identifythe status of the components on the network. In this way, the softwarearchitecture can function to inform all of the nodes on the network ofthe presence, capabilities, and status of the other nodes.

The software architecture 1018 can comprise multiple modules, each ofwhich has different functionality. Various combinations of the modulesor all of the modules can reside on each of the components. One modulehaving a basic or core functionality resides on all of the components.In one anticipated configuration, all of the modules reside at least onthe main controller, which establishes the main controller to functionas a primary or main software architecture, with the other nodesfunctioning in a client relationship to the main software architecture.In such a configuration, all of the nodes can communicate through themain software architecture. The software architecture can besufficiently robust that it can permit configurations without a mainsoftware architecture or with multiple main software architectures. Forexample, the controllers of the various components can work together tocontrol the operation of the appliance without any one of the appliancesfunctioning as a main controller. Regardless of the configuration, anycomponent with the software architecture can function as a client withrespect to the other components.

Because of the software architecture 1018, the internal components ofthe appliance are not only connected with one another, but the internalcomponents can also be connected to one or more external components or anew internal component through the network. The external componentand/or the new internal component has one, some, or all of the softwarearchitecture modules in resident. As a result, the external componentand/or the new internal component can communicate with the internalcomponents of the appliance and can also communicate with other externalcomponents having the software architecture.

The software architecture can be any suitable software architecture thatenables communication between the internal components of the applianceand the external component and/or the new internal component or betweencomponents external to the appliance. An example of the softwarearchitecture is disclosed in Patent Cooperation Treaty PatentApplication No. PCT/US2006/022420, titled “SOFTWARE ARCHITECTURE SYSTEMAND METHOD FOR COMMUNICATION WITH, AND MANAGEMENT OF, AT LEAST ONECOMPONENT WITHIN A HOUSEHOLD APPLIANCE,” filed Jun. 8, 2006, andincorporated herein by reference in its entirety, as published inWO2006135726. A related example is shown in priority document U.S.Patent Application No. 60/595,148, filed Jun. 9, 2005. All of thecommunications between components and accessories and/or any combinationof components and accessories described in this application can beimplemented by the software and network structures disclosed in eitherof these applications.

The software architecture disclosed in the aforementioned references canbe implemented by providing one or more of the software elements of thesoftware architecture at least on each of the components to becontrolled and on the accessory. The software architecture is configuredto generate a plurality of messages, with at least one of the softwareelements residing in each of the components and in the accessory andconfigured to enable transmission of at least one of the plurality ofmessages between the components and between the accessory and thecomponents. The messages can be transmitted for bi-directionalcommunication between components and/or components and accessory. Themessages can include command messages that are used to implement aphysical domestic operation cycle of the appliance. It will beunderstood that the consumable or at least the consumable holder can beconsidered a component on the network, for use in conjunction with theappliance having the software architecture.

Operation Cycles

An operation cycle comprises a set of physical actions that theappliance 12 executes in response to a cycle architecture for operationof the appliance. For example, a washing machine can have several washcycles that depend on the type of fabric being washed or a size of afabric load. Similarly, an oven can have several cooking cycles thatdepend on the type of food being cooked and the cooking process (e.g.,defrosting, baking, self-cleaning). Typically, the appliance whenpurchased by the user has a set of operation cycles that can permanentlyreside in the appliance as firmware.

Referring now to FIG. 3, an operation cycle component 60 can storeadditional operation cycles, changes not originally provided with theappliance 12, or other information upon which a cycle of operation canbe changed, and communicate with the appliance 12 such that theappliance can implement new, changed or additional operational cycles.An operation cycle stored by the operation cycle component 60 can alsoor alternatively include an updated operation cycle. The operation cyclecomponent 60 can be any type of component, such as a hardware devicethat can plug into the appliance 12.

The operation cycle component 60 can be a smart coupler that can couplewith both a personal computer and the appliance 12. See the discussionof smart coupler below. Any other suitable connector and/orcommunication method can be used. More particularly with respect to aconsumable holder 16 according to the invention, the operation cyclecomponent 60 can be the optional client 40 in or connected to theconsumable holder 16.

With continued reference to FIG. 3, the additional operation cycles,changes to existing cycles, or other relevant information can beuploaded to the operation cycle component 60 in any suitable manner. Forexample, the operation cycle component 60 having the relevant data canbe purchased at a retail store 62, or the information can be uploaded tothe operation cycle component 60 at the retail store. Alternatively, theuser can download additional operation cycles, changes, or relevant datavia the internet 64. For example, the user can download additionaloperation cycles through a personal computer 66 and then upload theadditional operation cycles to the operation cycle component 60 or theuser can wirelessly directly download the operation cycles to theoperation cycle component 60. In another embodiment, the user candevelop custom additional operation cycles or changes on the personalcomputer 66 and upload the custom additional operation cycles or changesto the operation cycle component 60. In an alternative embodiment,additional operational cycles can be transmitted wirelessly from thepersonal computer 66 to the appliance 12 without using a separateoperation cycle component 60, in which case the personal computer 66 mayitself be considered the operation cycle component. The wirelesslytransmitted additional operational cycles can be transmitted to anintermediate storage in the appliance 12. The cycles can also beauthenticated by the software architecture or other methods to ensurethat they are compatible with and appropriate for the appliance.

The operation cycle component 60 can couple with the appliance 12 in anysuitable manner, such as through a direct hardwire connection or awireless connection. Furthermore, the appliance 12 can implement theadditional operation cycles, changes or relevant information directlyfrom the operation cycle component 60 or the relevant data can betransferred from the operation cycle component 60 to the appliance 12 orto the consumable holder 16.

FIG. 4 illustrates a typical controller 68 or control board of theappliance 12, one or more of which can be connected on a network, and towhich additional operation cycles can be provided by an operation cyclecomponent 60. Appliances can have one or more control boards controllingthe cycle of operation and the user interface as shown in FIG. 8 items1010, 1012, and 1020. Among other things, the controller 68 will includea cycle architecture 69. The cycle architecture 69 differs fromconventional operational cycle execution software. Conventionaloperational cycle execution software is determined wholly from compiledsource code that cannot easily be separated into constituent parts orportions. The cycle architecture 69 is software that has two distinctportions, a cycle structure 71 and a cycle engine 73. The cyclestructure 71 is a data or cycle structure portion representing aplurality of elements or components comprising an ordered collection ofsteps, separated from each other by transition conditions, with theactions to be taken during each step. Each element or component can havean identifier to enable replacement or merging of elements orcomponents. The transition conditions are the conditions under which aselected step should transition to a next step in the ordered collectionof steps. Transition conditions comprise arbitrarily complex logicexpressions that must be resolvable to a Boolean value. In oneembodiment, the logic of a Transition Condition is a composition ofstructures comprising operators connected to functions, other operators,variables, or constants and functions connected to other functions,operators, variables, or constants wherein the composition forms acomposite which can be resolved to a Boolean during the cycle ofoperation. For example, a logic expression could start with a structurerepresenting an “AND” wherein the “AND” is connected to one “OR”structure and a function “foo”. The “OR” structure is then connected toa function “bar” and a function “domo”. During the cycle of operationwhere a first step was separated from a second step by the TransitionCondition, the first step would de-activate and transition to the secondstep when function “foo” returned a value of true and either functions“bar” and “domo” returned a value of true. Compositions of structuresrepresenting logic can be represented in data, which data can beconverted into the composition of structures during or before the cycleof operation. Likewise, existing compositions can be modified withadditional data. Using this data technique or another techniqueproviding the same flexibility, a cycle architecture comprising a cyclestructure further comprising a plurality of step transition logicexpressions can be authored by an authoring tool, transmitted vianetwork, encoded into a consumable or consumable holder, and used by acycle engine to execute a cycle of operation. The cycle engine 73 issoftware that can be combined with at least one cycle structure 71 inthe controller 68 for the execution of an operational cycle.

One advantage of a cycle architecture 69 partitioned into two componentsis that the cycle engine 73 can reside in a plurality of differentappliance types, thereby reducing the cost and increasing the quality ofthe appliance types. A second advantage is that new appliance models ortypes can be developed using the cycle engine 73, thus avoiding thedevelopment time and cost of conventional operational cycle executionsoftware, which is typically and historically developed specifically foreach new appliance model and type.

Another advantage of a cycle architecture 69 is that it can be incommunication with a cycle structure 71 over a network or within aruntime environment. This allows the logical architecture of theappliance to vary independently from the physical architecture of theappliance. In one embodiment, an embedded virtual router is used toprovide a messaging layer between all components of the cyclearchitecture including a cycle structure 71 and the cycle engine 73.This allows the manufacture of the appliance process control apparatus14 increased degrees of freedom with respect to the physical embodimentof the appliance process control apparatus 14 because the cyclearchitecture 69, when combined with an embedded virtual router, providesan adaptive function allowing the cycle architecture to route messagesthroughout the networks of the physical architecture without priorknowledge of the physical network or physical architecture.

Another advantage of a cycle architecture 69 using a cycle structure 71and a separate cycle engine 73 is that the cycle structure 71 isportable, which allows it to be delivered to the cycle architecture 69over a network, from a remote data source, from a local data source likeflash memory, EE memory, or Read-Only Memory, or from an accessory, froma user interface configured to create a cycle structure, or from anysource of information about a cycle structure or data about a cyclestructure including data about a consumable. One example for deliveringa cycle structure 71 is by the use of an operation cycle component 60 asshown in FIG. 3. This advantage provides upgradeability to the applianceoperational execution software in a less obtrusive approach than that ofconventional operational cycle execution software in that theoperational execution software can be changed in whole or in partwithout a complete re-downloading of the whole execution softwarerunning on the controller 68.

Another advantage of a cycle architecture 69 using a cycle structure 71and a separate cycle engine 73 is that the cycle structure 71 can bealtered to any degree even after the appliance is installed and in use.This type of upgradeability can be delivered to the user in a variety ofmethods such as by authoring tools, cycle accessories, consumables withencoded cycle structures, network downloads, appliance user interfaceconfigured data, software patches and the like, or even by an operationcycle component 60. Conventional operational cycle execution softwarecannot be changed without a complete re-downloading of the wholeexecution software of controller 68. Further, conventional operationalcycle execution software is configured to accept only parameters thatvary the magnitudes of time, temperature, speed, and the like, or modifyfixed actions within a fixed ordered collection of steps. By contrast,the cycle architecture 69 according to the invention is fullymodifiable, allowing for new steps, re-ordered steps, new actions, newor modified transition conditions and the like.

The cycle structure 71 can be represented directly or indirectly. Adirect representation of a cycle structure will provide an orderedcollection of steps, transition conditions and actions, either logicallyor in an instructions set that can be interpreted by a cycle engine 73.An indirect representation of a cycle structure 71 will provide a set ofinstructions that will enable a creator, a converter, a compiler, or thecycle engine itself to build an ordered collection of steps, transitionconditions and actions.

Whether direct or indirect, the cycle structure 71 can be represented ina plurality of data embodiments such as key-value pairs, XML, relationaldata tables, comma separated variable files, a hierarchical compositetree or graph, byte arrays, data packets, command objects, binaryencoded data, data encoded as a programming language such as a C headerfile, text, scripts, serialized objects, and messages. Regardless of theembodiment of the cycle structure 71, the essential meaning andfunctionality will be interpreted to accomplish the same operationalcycle execution on the controller 68. It is envisioned that a cyclestructure 71 may be transcribed from one embodiment to another asappropriate during the authoring, distribution, and delivery of thecycle structure to the cycle architecture 69 on controller 68 withoutloss of meaning or functionality. It will be understood that dataembodiments of a cycle structure 71 are transferable between and can beresident in a plurality of memory types including RAM, ROM, andRead-Write types like Flash, EE, RW CDs, floppy disks, hard drives,portable memory thumb drives, external hard drives, and the like.

For an indirect representation of a cycle structure, a cycle structurecreator can read a set of instructional messages, for example, andinterpret them to build or create a cycle structure. Such instructionalmessages can be in the form of data packets for messages preferably inaccordance with software architecture such as that of the incorporatedWO2006135726. For example, the data packets can have routing informationsuch as an enabling identifier, one example of which can be a functionalidentifier representing things like a cycle structure creator, a state,a transition condition, or an action. As well, the data packets couldhave a collection of command identifiers that are supported via acollection of Op (“Operation”) Codes.

In an additional form of indirect representation, a cycle structure 71can be the source data for automatically generated compilable sourcecode, or the cycle structure itself may be formatted such that it isdirectly compilable by a compiler configured to create an executableprogram appropriate for the controller 68.

Yet another form of indirect representation can be a plurality of cycleparameters like time temperature, speed, fill amount and the likewherein the cycle engine or an arbitrary software component wouldreceive the cycle parameters and convert them to a direct representationof a cycle structure 71 or portion thereof.

In another form of indirect representation, a cycle structure 71 can berepresented as a script that is either compilable for the controller 68or interpretable by a cycle structure creator or converter (see FIG.21). A script can be created by a script authoring tool for introductioninto the use environment in any of the disclosed embodiments. The scriptin communication with cycle architecture 69 is able to affect and changethe state of the appliance control system as described herein.

For a direct representation of a cycle structure where a data packet isused to deliver information about a cycle structure, the data packet cancomprise routing information and a direct representation of a cyclestructure. The direct representation could be encoded into a byte array.The byte array could then be operated on directly from a cycle engineconfigured to interpret the byte array by decoding the byte array duringthe interpretation such that the data in the byte array could beinterpreted as an ordered collection of steps separated by transitionconditions having transition logic wherein each step comprises aplurality of actions.

Another example of a direct representation is the script is shown below.The script comprises information about the consumable and informationabout a cycle structure including references to functions, variables,memory locations, APIs and messages directly available or exposedthrough an embedded virtual router in the appliance controllers 68,information about credentials such as a password (not shown), andinformation about the script such as a CRC (not shown). The script canalso comprise a set of basic instructions like operators likeIFLESSTHAN. The cycle engine 73 can validate the script against thereferences making sure that the appliance controllers 68 can support thereferences called for by the script. For example GRILL could represent asoftware class having a set of functions that can be invoked if aninstance of the class is available. The script statement $resource grillinstructs the cycle engine 73 to associate the variable grill with theinstance of GRILL wherein if the object already exist then theassociating is one of referencing grill with GRILL and wherein if itdoes not, to instantiate GRILL and then create the reference from grillto GRILL. If there is no GRILL capability or functionality or there isnot a GRILL class available, then the cycle engine 73 would reject thescript and notify the user of the rejection using a user interface andprompt the user to manually specify the operating instructions for theappliance 12 using the user interface instead of the script. Otherreasons that a script might be rejected include insufficient memory tohold or execute the script, non-existent references (shown as $resourceor $var), unreadable script, and script that does not conform to itsCRC, or non-credentialed script which is script that can not beauthenticated using the credentials of the script. The script comprisesfunctionality enabling it to perform all essential functions aspreviously described in the embodiment of the cycle structure comprisingsteps, actions, transition conditions, and transition logic expressions.The statement RESOURCEACTION grill.turnOn is an example of an action.‘IFLESSTHAN time,2000’ is an example of transition logic evaluating to aBoolean value. LABEL1 and LABEL2 are examples of steps.

Additionally, a script could comprise information identifying theplurality of appliances to which the script could be used so that thecycle accessory shown and described in FIGS. 3 and 10 could hold aplurality of scripts each comprising the information so that theaccessory could apply the appropriate script to the cycle architecture69 when it establishes communication with an appliance.

+Header

exp-date: “09/09/09”

brand: “La Cucina Italiana”

advertising: “The taste of Italy in your mouth”

$var time,2

$var temp, 2

$resource timer, TIMER1

$resource cookbroil, COOKBROIL

$resource grill, GRILL

$resource temp-oven, TEMPERATUREOVEN

$resource ui, UI

$resource beep, BUZZER

+Behavior

RESOURCE ACTION timer.init,250

RESOURCE ACTION timer.start

RESOURCE ACTION ui.showAdvertsing,brand, advertising

LABEL1:

RESOURCE ACTION timer.getCounter

MOVE time, ANSWERACTION

IFLESSTHAN time,2000

GOTO LABEL1

RESOURCE ACTION timer.stop

RESOURCE ACTION ui.showCookingScreen, “Cooking Lasagna”

RESOURCE ACTION cookbroil.start, 400 F, 10

LABEL2:

RESOURCEACTION cookbroil.getStatus

MOVE temp, ANSWERACTION

IFNEQUAL temp, FINISHCOOKING

GOTO LABEL 2:

RESOURCEACTION ui.showCooking Screen, “Cooling down”

LABEL3:

RESOURCEACTION temp-oven.getTemp

MOVE temp, ANSWERACTION

IFGREATERTHAN temp, 200

GOTO LABEL3

RESOURCEACTION ui.showCookingScreen, “Making it crispy”

RESOURCE ACTION timer.start

LABEL4:

RESOURCE ACTION timer.getCounter

MOVE time, ANSWERACTION

RESOURCEACTION grill.turnOn

IFLESSTHAN time,180000

GOTO LABEL4

RESOURCE ACTION timer.stop

RESOURCEACTION grill.turnOff

RESOURCEACTION ui.showCookingScreen, “Your Lasagna is done. Wait forcooling it”

RESOURCEACTION timer.start

LABEL5:

RESOURCEACTION timer.getCounter

MOVE time, ANSWERACTION

IFLESSTHAN time, 120000

GOTO LABEL5

RESOURCEACTION ui.showCookingScreenDone, “Your lasagna is done! Enjoyit”

RESOURCEACTION beep.longBeep

The functionality of the script is shown in FIG. 22 and is describedherein. At steps 400, 402 and 404, respectively, a timer is set,initiated, and the brand and advertising defined in the script (here,“La Cucina Italiana” “The taste of Italy in your mouth” is displayed onthe user interface (UI) for the defined time. At the end of the settime, the timer is stopped at 406, and the UI is instructed to display“Cooking Lasagna” at 408, while a cooking cycle (broiling) commences at410. At the end of the cooking cycle (ascertained by temperature), theUI is instructed to display “Cooling down” at 412. At the end of thecooling down period (ascertained by temperature), the UI is instructedto display “Making it crispy” at 414 while the timer starts at 416 andthe grill is turned on at 418. At the end of the set time, the timer isstopped at 420, and the grill is turned off at 422. The UI is instructedto display “Your Lasagna is done. Wait for cooling it” at 424. The cooldown cycle is ascertained by a preset timer at 426, after which the UIis instructed to display “Your lasagna is done! Enjoy it.” at 428 andthe cycle terminates.

It is contemplated that a cycle architecture 69 can have multiplesources of information about and/or representing a whole, a part of, ora modification to a cycle structure and that each source may either be adirect or indirect representation and that each source may be embodiedin a variety of memory types. According to the invention, theinformation about a cycle structure will be used to change a cyclestructure in the appliance and thereby change an operation cycle of theappliance. The term “change the cycle structure” is contemplated toinclude creating a cycle structure, modifying a cycle structure, oraccessing a whole or part of a cycle structure or a representation of acycle structure.

It is further contemplated that the cycle architecture 69 may publishdata about itself, its progress and information about the progress. Forexample, cycle architecture 69 can publish its current active step,conditions about the transition logic, elapsed time per step, totalelapsed time, or sub-states of the steps, or sub-states of anordered-collection of steps such as fault state, normal state,transitioning state, idle state, etc. The cycle architecture 69 mayimplement additional functionalities such as a software or network APIallowing cycle architecture observers to register for notifications toreceive the published data.

In a first embodiment, the cycle engine 73 is compiled software thatcommunicates at runtime with at least one source of indirect or directrepresentation of a whole or part of a cycle structure 71(a) and buildsor changes an in-memory cycle structure 71(b) where the memory is incommunication with the controller 68. Once the in-memory cycle structure71(b) is prepared, the cycle engine 73 finds the initial step, reads thestep, executes the actions prescribed by the step, and begins evaluatingthe transition logic for transitioning to the next step, whereupon theprocess repeats in subsequent steps.

In a second embodiment, the cycle engine 73 is compiled software thatcommunicates at compile time with at least one source of indirect ordirect representation of a whole or part of a cycle structure 71(a) andbuilds or changes downloadable image comprising a cycle structure 71(b).Once the compilation is complete and the downloadable image isdownloaded to the memory of the controller 68, the cycle engine 73 findsthe initial step, reads the step, executes the actions prescribed by thestep, and begins evaluating the transition logic for transitioning tothe next step, whereupon the process repeats in subsequent steps.

In a third embodiment, the cycle engine 73 is compiled software thatcommunicates at runtime with at least one source of indirect or directrepresentation of a whole or part of cycle structure 71(a) withoutbuilding or changing a cycle structure 71(b). Once in communication, thecycle engine 73 immediately commences execution by continuouscommunication with the source whereupon it finds the initial step, readsthe step, executes the actions prescribed by the step, and beginsevaluating the transition logic for transitioning to the next step,whereupon the process repeats in subsequent steps.

In a forth embodiment, the cycle engine 73, uses a fetch and executetechnique to conserve memory. In this embodiment, the cycle engine 73 isin communication with a source of information about a cycle structure71(a) where a first memory comprises the source and a second memorycomprises the cycle engine 73 so that the cycle engine can fetchportions of the information from the source and convert that portion toa form appropriate for execution by the cycle engine. In one example ofthis embodiment, the cycle engine 73 would fetch a portion of theinformation representative of future potential steps, transitions,actions, and transition logic expression or information that representsthe information so that the cycle engine can expeditiously transition tothe next step based on a step transition because the next step isalready in the form appropriate without the latency involved in a memoryread or network message. Contemporaneous to the step transition, a nextportion will be fetched and the process of fetch and execute repeats.

It should be understood that all communications according to theembodiments may be accomplished using an embedded virtual router,gaining the advantages describe herein.

The cycle architecture 69 can be communicated, as well as be configuredto communicate with a client to receive and send messages by routinginformation such as an enabling identifier, one example of which can bea functional identifier representing things like a cycle structurecreator, a state, a transition condition, or an action. As well, themessages could have a collection of command identifiers that aresupported via a collection of Op (“Operation”) Codes. Preferably, thecycle architecture 69 of any embodiment will receive messages from aclient allowing for changes to the cycle structure 71. Changes to acycle structure may, for example, include the insertion or deletion ofsteps, additions or deletions to the actions of each step, or changes tothe transitional logic between any two given steps. To accomplish suchchanges, identifiers must be associated with the components of the cyclestructure such that the client messages can fully specify the exactdesired modifications to the cycle structure.

The actions of the cycle architecture 69 cause the state of theappliance control system to change including, inter alia, changes to theappliance process control apparatus 14, a user interface, appliancesoftware, and other components of the appliance like the screens on anappliance graphical user interface or some graphical component thereon.Other exemplary actions include changing the state of electro-mechanicalactuators like relays, valves, and fans, and changing the state of userinterface indicators like LEDs, buzzers, light rings, segmenteddisplays, or graphics on a graphical LCD. Additionally actions of thecycle architecture 69 further comprise effects including hiding ormaking available user interface screens, making elements of screensvisible, invisible, enabled, or disabled; changes to fonts, colors,size, or other attribute values of screen elements, changes to menu sothat items could be enabled, disabled, added, and deleted, and the like.The devices to which the actions will apply may be represented asidentifiable functions with a known controllable interface. As disclosedin the incorporated WO2006135726, physical devices may be modeled orvirtually revealed in the software architecture (“SA”) by an API(“Application Programming Interface”) Id where their control interfacesare represented by a collection of Op Codes, each having associatedparameters. This allows controllable devices or software components thatcontrol the controllable devices to expose themselves to the actions ofa step as a message, such that location of the control software that canoperate on a device or the control software providing controllableaccess to the device does not need to be known by the cycle engine 73.An embedded virtual router (EVR) can provide communications between thecycle architecture 69, controllable devices having a control interface,and software components that control the controllable devices (devicedrivers) wherein the router provides a messaging interface between theactions of the cycle architecture 69 and the devices and the softwarecomponents that can implement that action regardless of where thedevices or software components reside. This capability allows the cyclearchitecture 69 to interact with devices, appliances, and softwareincluding other cycle architectures that reside on a differentcontroller 68 or in a different appliance 12 or in a different device incommunication with the cycle architecture 69 such as any external client1004 having either the software architecture 1018 or the softwarearchitecture driver 1016. “Software components” here means any software,algorithm, or logic directly or indirectly associated with theoperational cycle of an appliance. Generally, all logic providesindirect access to the control of a device, but the meaning can extendto include any non-device oriented software like fragmentationalgorithms, user instructions, network authentication services, and thelike.

Routing information comprises identifiers allowing a sender to send amessage to a receiver. Examples of identifiers which enable routing arenetwork node ids which are identifiers identifying the address of eitherthe sending or receiving node on any given network. An example ofnetwork node id is shown in the address byte of FIG. 4 (as disclosed inthe incorporated WO2006135726). Another example of an identifier whichenables routing is a network id uniquely identifying each network withina plurality of networks such that a sender could uniquely identify thedestination (or receiver) of a message by with a network id and anetwork node id thereby allowing the network node ids on each networkvary independently while maintaining unique addressability by thecombination of network id and network node id. Another example of anidentifier which enables routing is an Object ID and Method ID or an APIID and Op Code. These identifiers provide routing from the sending nodeto the receiving software module or object within the receiving node.These identifiers provide unique addressability within the softwareoperating environment of a node. A routing table comprising a pluralityof rows can be constructed having a combination of routing informationidentifiers in each row where each row represents a route. An additionalunique identifier (a route id) can be added to each row identifying eachroute thereby providing the sender a convenient mechanism for sendinginformation. An example of a routing table is shown here:

Routing ID API ID Sub-Net ID Sub-Net Node ID 4 35 1 1 5 46 2 2

Software can be constructed allowing the sender to send information to aroute id whereby the software with convert the route id to theappropriate routing identifiers such that the information is sent to theappropriate network and to the appropriate node on the network and tothe appropriate receiving software module. In a further example whereina sender on a first node communicates to a receiver on a third node viaa second node, the second node can have a routing table linking, forexample, the Object Id to another route id so that the message sent bythe first node is appropriately propagated and routed to the third nodeby software on the 2^(nd) node using the routing table of the 2^(nd)node. Routing tables can be populated with routing information using thetechniques described herein.

The foregoing discussion of cycle structures will be helped by anunderstanding of an embedded virtual router (EVR) in the invention. FIG.30 is a schematic illustration of a virtual router showing a mappingbetween a pair of software architecture implementations. The virtualrouter of FIG. 30 is a software design which encapsulates the APIimplementations (objects, see APIs 1-8 in each side of the router ofFIG. 30) of the software architecture 10 such that the collaborationbetween an embedded client (application logic, algorithms, closed loops,sequencers, and state machines) and embedded components (the softwarearchitecture 10 API implementation: objects like defrosters, heaters,temp sensors, valves, etc.) is uniform and identical regardless if theentities collaborate over the network or share a runtime environment(the shared runtime collaboration being an example of a virtualnetwork).

FIG. 30 shows six unique collaboration examples labeled as suchillustrative of how a pair of software operating environments 916Aexisting on separate hardware components 916 and connected by a network914 will use the various software components 916B of the softwareoperating environment 916A to create transparent access between theoperating logic of 959 and the software components 916B of both theright hand and the left hand software operating environments.

Prior to describing the collaboration examples, a description of thestructure of FIG. 30 should aid in the understanding of thecollaboration examples. Each software operating environment 916Acontains representations of a sub-set of useful software operatingcomponents (916B) contained, including: the software architecture 10,internal communications network layer interface 952, a sub-component ofthe software architecture 10, the DAQ 930, and a hardware abstractionlayer 980.

The hardware abstraction layer 80 comprises: a mechanism therein toencapsulate the particular fixed address of the connected electricalcircuits on which the software operating layers of the hardwareabstraction layer 980 will operate and software interfaces (928, 928A,or 982) encapsulating occurrences of 916B in the form of one of thefollowing: the packetized representation (an ordered collection ofbytes) of a message 928 exchanged by the software architecture 10, thepacketized representation (an ordered collection of bytes) of a messageexchanged by the software architecture 10 representing only the payloadstructure 928A (the valid data arguments) expected by the softwareoperating component 984 or 986, or an alternate representation 982 ofeither 928 or 928A where the intent and data values and resultantactions are functionally identical but not of the form of an ordercollection of bytes. A unique software function 982 has argumentsrepresented by individual named variables whose value is derived from928A or represented by an ordered collection of bytes derived from 928A.

Application GDMs 984 are variants of 916B known as global design moduleswhich are standard software operating components having been subjectedto a standard development process including functional andnon-functional requirements, testing, documentation, and implementationguidelines. Application GDMs 984 address appliance specific concernssuch as defrosters, heaters, and door closure. Application GDMs 984 canbe classified into at least two types of variants. The first variantcontains specific application logic apart from the application logic 959that is used to govern the behavior and gather information from acollection of other software operating components including a pluralityof other GDMs 984, 986. The second variant contains specific applicationlogic apart from the application logic 59 that is used to govern thebehavior and gather information from a specific electro-mechanicaldevice or sensor such as a heater, evaporator, motor, valve, solenoid,relay, pressure or temperature sensor. The second variant can beconfigured to address specific concerns made relevant by the specificmanufacturer's variant of the device, by the particular configuration ofthe device based on the usage mode determined by the applicationrequirements (i.e. scaling values), or by a confluence of factors whichcreate specific concerns not mentioned heretofore.

Infrastructure GDMs 986 address specific recurring concerns which areindependent of the application of the system architecture. They can bere-used across a plurality of appliances, examples of which include butare not limited to refrigerators, cooktops, dishwasher, dryers, andclothes washers. Infrastructure GDMs 986 can be classified into at leasttwo variants. The first variant is associated with a particular concernresulting from a recurring combination of electrical components orelectrical constraints. Some examples are: manufacturer interfaceconstraints, device duty cycles, electrical load characteristics (suchas inrush and steady state current limits), or other constraints such asthe mode of analog-to-digital conversion such as 4-20 mA current loopsvs. 0-5V dc analog voltage feedbacks. The second variant is associatedwith appliance- and application-independent software components known asutility functions. They provide logic used by other 916B componentsincluding 959 and 980. The second variant can contain or use referencesto the first variant of the infrastructure GDM 986. Examples includetimers, zero cross detection, and other useful software components whosepurpose is more utilitarian than driven by application orelectro-mechanical requirements.

An embedded virtual router 970 provides an encapsulating layer by whicharchitectural dependencies (the method by which one software component916B is accessed by or exposed to another 916B (examples of 916B are930, 984, 986) within or between at least two software operatingenvironments connected by the network 914 alone or a combination ofnetwork 914 and other networks) between the application logic 959 (ofthe software operating layer 916A of the component 916) and thecomponents comprised by the hardware abstraction layer 980, DAQ 930,another instance of application logic 959 or component therein, or anyother useful component 916B are minimized or eliminated.

A software component 972 can be used by other software components 916Bto obtain references to any other software components 916B where theobtained 916B may be part of a software operating environment 916Aexisting in or on: the same hardware component 916, a different hardwarecomponent 916 connected by 914, a different hardware component 922connected by a combination of network segments including 914, or adifferent hardware component 916 of a different appliance 12 connectedby 914, a combination of different network segments between the twooccurrences of 12, and the 914 of the first appliance 12.

The software component 972 also provides the mechanisms for othersoftware components residing within the same software operatingenvironment 916A to publish the necessary identification and/or routinginformation into the memory of 972 to enable the aforementionedenumerated uses of the software component 972. The identification androuting information may be associated with components residing withinthe same software operating environment. Alternatively, theidentification and routing information can be associated with componentsapart from the components residing within the same software operatingenvironment but that are known by components residing within the samesoftware operating environment.

Structures 974 in the memory of 970 are able to receive messages orprovide functions for invocation of messages and are able to sendmessages or provide callback functions for the distribution ofinformation. These structures have an access definition of a packetstructure 928, a payload structure 928A, or 982 corresponding to anoccurrence of a software component such as components within thehardware abstraction layer 980, application logic 959, or any otheruseful software component located in the aforementioned enumerations of972 and the capability to route the information to that softwarecomponent or to an appropriate intermediate software component havingthe same or similar purpose of 974.

Looking now at the possible collaboration examples, it is expected thatthe structures 974 of 970 will be created and populated based ondiscovery queries containing requests for access to specific softwarecomponents 916B which are both identifiable and routable, invocationsimplying said access, or by software components 916B which are able toinvoke on 970 on behalf of themselves or other components 916B resultingin creation and population of structures 974.

Collaboration 1: a command is issued by software component 959 of theright-hand software operating environment 916A and received by asoftware component contained in the collection of 974 with an identifierof API 1 within component 970 of the same software operatingenvironment. Using the identification and routing information containedwithin 970, the component identified by API 1 transmits the receivedinformation through the other local software operating layers 10 and952, and finally transmitted over 914 and received by 952 of left handsoftware operating environment. The message is then handled by softwarearchitecture 10 and routed to the appropriate component within 974 ofthe left hand software operating environment. The appropriate 974 of theleft hand software operating component using identification and routinginformation contained within 970 of the same software operatingcomponent then invokes on or sends the message to the localimplementation of API 1 contained in the left hand software operatingenvironments hardware abstraction layer 980. Thus the application logicwithin software component 959 of the right hand software operatingenvironment invoked a function implemented in the software operatingenvironment of the left hand side without information contained thereinfor the realization of said invocation. Therefore, the value of thedesign implied by FIG. 30 is that application logic 959 is re-useablewith respect to the location of the of the other software operatingcomponents 916B within a plurality of software operating environments916A connected by a network 914 or a plurality of network segments whichmay include 914.

Collaboration 2: In this case, the initiation of the message is from 959of the left hand software operating environment 916A. Illustrated is thecase where the final invocation is on a software component (in this caseAPI 2) within the same software operating environment using the samemethodology described in greater detail in Collaboration 1. Therefore,in Collaboration 2, an alternative architectural disposition between anoccurrence of Application logic 959 to some other useful softwarecomponent (API 2 of hardware abstraction layer 980) is shown to have noeffect on the implementation of either. And furthermore, it is thepurpose of software component 970, also being able to comply with theIdentification and interface requirements imposed by the softwarearchitecture 10, to provide this capability.

Collaborations 3-6 show additional uses for the embedded virtual router970. The mechanisms used to accomplish these variants are the same asdescribed in Collaborations 1 and 2. They are included to illustrate theusefulness of the design and the expected additional message patterns tobe available with respect to the DAQ 930. Local event listeners (3) andremote event listeners (4) of application logic 959 are provided with aninterconnection to a representation of the DAQ engine 930 providing notonly a connection to the DAQ in the local software operatingenvironment, but also to the DAQ(s) which reside in remote operatingenvironments. DAQ generated messages based on the occurrence of DAQevents can be transmitted locally (6) and remotely (5) throughmechanisms available in 970.

In addition to the six collaboration examples, a seventh collaborationexample includes first and second arbitrary software componentscomprised within the application logic 959 where both the first andsecond arbitrary software components have identifiers and can beidentified within the structures 974, which can comprise the routingtable. In this collaboration, the first arbitrary software componentsends a message to the second arbitrary software component by invoking asoftware function linked to a plurality of function pointers within therouting table (another example of using a virtual network, i.e. acollaboration between arbitrary software components within a sharedruntime environment). One of the function pointers of the plurality offunction pointers links the message to at least the second arbitrarysoftware component. Likewise, if there is a second instance of thesecond arbitrary software component residing in the application logic of916, the first arbitrary software component function invocation may notchange. In this case, the plurality of function pointers would include apointer linking the invocation to routing information contained in therouting table. The routing information is necessary for enabling themessage to be routed from the invocation to the receiving secondinstance of the second arbitrary software component.

It is preferred that the routing tables are populated by one of at leastdiscovery confirmation messages, propagated discovery confirmationmessages, manual configuration, semi-manual configuration, hard codedconfiguration software, and the software compilation process. It shouldbe noted that using discovery messages to populate routing tables is thepreferred embodiment. However, routing tables can also be populatedusing conventional configuration methods involving a manual orsemi-manual configuration process, such as with the use of a visualconfigurator (see, for example, FIGS. 28 and 29 used for anotherpurpose). In addition, a manual or semi-manual configuration process canbe used in addition to discovery generated routing tables. In thisapproach, the discovery process or the configuration process canincrementally add or delete routing information within a routing table.

The various techniques described above with respect to the use of theembedded virtual router 70 can also be applied in a variety of othernetwork configurations in order to enable communication between objectsin the system. Examples include but are not limited to enablingcommunication between two different arbitrary software components withinan application logic 959, an arbitrary software component of anapplication logic 959 and an arbitrary software component of a hardwareabstraction layer 980, any arbitrary software component of a firstprocessor and any arbitrary software component of a second processor onthe same component 916, any arbitrary software component of a firstprocessor and any arbitrary software component of a second processor ondifferent components 916 within an appliance 12, any arbitrary softwarecomponent of a first processor and any arbitrary software component of asecond processor on different components 916 in different appliances,any arbitrary software component of a first processor and any arbitrarysoftware component of a second processor on different computers wherethe computers can be dislocated from one another but coupled via anetwork.

It should be understood that the arbitrary software components above arepreferably associated with an identifier associated with thefunctionality of the software component (a class) and with an arbitraryidentifier used as an object handle. A comprehensive namespace cancontain unique identifiers for each arbitrary software component on thesystem. An exemplary namespace can create identifiers comprising a classID including an API ID, an instance ID, and a type ID; and an object IDcomprising a node ID and an instance ID. In another exemplary scheme,model number ID and serial number ID can also be identifiers in anamespace. Other namespace schemes can use any desired combination ofidentifiers to give each arbitrary software component a uniqueidentifier.

FIG. 31 illustrates a network architecture comprising two appliances3012, 3012′ and a third party device 3022 of the type shown in FIG. 1.Each appliance has a plurality of nodes 3016 comprising, in thisembodiment, a CCU, a user interface UI, and several peripherals P1, P2,and P3 in communication with each other by a local network 3014. Eachperipheral can be a circuit board which may or may not have at least onemicro processor. On the UI board, there are shown two micro-processorsuPI and uP2, connected by a serial communication bus which is differentfrom 3014. The UI board typically has multiple network connections onUSB, WIDE, and SPI networks. The third party device 3022 may be able tosend messages. Alternately, the third party device 3022 may sendmessages in the form of a taxonomy dataset. In the latter case, theperipheral P3 could contain a taxonomy architecture which could createwell formed commands. The appliances 3012, 3012′ communicate with eachother over network 3021 and the third party device 3022 communicateswith the appliances over network 3020.

It will be seen in FIG. 32 that messaging can occur among microprocessors on the same board connected on a network different from 3014.As well, messaging can occur between boards 3016 on at least twonetworks where the networks are not of the same type. Further, messagingcan occur between appliances 3012, 3012′ between boards 3016 carried onat least three networks where at least one of the three networks is anetwork external to the appliance. Yet further, the third party device3022 can communicate with nodes implementing SA or nodes that can routemessages to a node implementing SA in accord with the invention.

It will be understood that the architectural characteristics of anetwork configuration normally impact the implementation of thearbitrary software components which communicate within the architecture.By “architectural characteristics”, we refer to the distinctive featuresof individual networks, the way the various boards 3016 areinterconnected, and the combinations of network routes interposedbetween connected boards 3016. An embedded virtual router in a processoron a board 3016 in accord with the invention will enable the arbitrarysoftware components in that board 3016 to communicate independently ofthe architectural characteristics of the associated networks.

An advantage of an embedded virtual router according to the inventioncan be seen in an appliance having a plurality of useful arbitrarysoftware components, each providing at least one useful consumerbenefit. Since different consumers typically prefer differentcombinations of features, it has been a long standing problem in theappliance industry to be able to supply only the sub-set of specificfeatures that an individual consumer would prefer. Typical approachesinclude (1) providing multiple appliance models or SKUs, each with aunique feature set, and (2) providing an appliance with the superset offeatures insuring that the customer can have all the available features.Both are costly because arbitrary software components in appliances arehardware dependent; at a minimum, software for a board controlling adevice in an appliance must be reworked for use in a differentappliance, even if it is the same or similar device. This inventionprovides a third, more cost-effective alternative. With the use of anembedded virtual router according to the invention, all arbitrarysoftware components are independent of one another with respect to theirarchitectural location. An appliance manufacturer can thus provide auser-specific capability for an appliance at much lowest cost byproviding an external client having any combination of arbitrarysoftware components that can be purchased separately as part of anexternal accessory, but with full capacity to participate in all formsof useful communication with other arbitrary software components withinthe appliance because of the embedded virtual router.

Assume, for example, an appliance with three possible features: (a) adoor switch, (b) an LED, and (c) an LCD, either or both of the LED andthe LCD to indicate the state of the door switch. All versions of theappliance will have a door switch. But some will have only an LED, somewill have LCD, and some may have both an LED and an LCD. With the priorart, the manufacturer has to provide three software architectures: onefor communication between the door switch and the LED, one forcommunication between the door switch and the LCD, and one forcommunication among the door switch, the LED and the LCD. With anembedded virtual router according to the invention, designer need onlyhave software architecture for the door switch and an embedded virtualrouter. An accessory can enable the door switch in any version of theappliance having an embedded virtual router to handle communication withany combination of LED and LCD, without further software architecture.

For another example, assume an appliance with three controller circuitboards, each having a feature. If a manufacturer sought to save costs bycombining two features on a single board, any costs savings would havebe adjusted by the added cost of reconfiguring the software architectureon the third board. A software architecture with an embedded virtualrouter according to the invention would enable such a change without thenecessity of reconfiguring the software architecture.

FIG. 33 illustrates the process of creating the main structures 974 ofthe embedded virtual router 970 (see FIG. 30). The three main structures974 comprise a capability table, a dependency table, and a routingtable. Each software module operating over the appliance network oramong appliances and accessories contains its own capability anddependency information. The compiler pre-processor executes a set of EVRbuilder macros at compile time to create a capability table and adependency table (that may be in composite form) for the downloadablesoftware image. Reveal Discovery completes the process by populating therouting table. Although FIG. 32 shows the creation of the dependency andcapability table on compiling, all can be created at runtime. Therouting tables simply inform the application layer how to ‘get to’ othersoftware specified in its dependency list. Routing tables are populatedbased on a first set of software modules stating a set of “needs” in thedependency table and a second set of software modules stating a set of“haves” in the capability table. For “needs, the implementer specifieswhat software modules (classes) are needed by this software module. For“haves”, the implementer specifies what software modules (classes) areavailable.

FIG. 33 illustrates how the embedded virtual router 970 can enabledifferent hardware components 916, 916′, 916″ to be virtually chainedtogether. This virtual chaining enables messages to be sent from theapplication logic 959 of a first hardware component 916 to theapplication logic 959 of a third hardware component 916″ without thefirst hardware component 916 having to know anything about the routethat a message will have to take by using structures 974 contained ineach component's embedded virtual router 970. Each hardware component916 916′, 916″ includes at least one arbitrary software component, e.g.,software components 1060 (see FIG. 8). Each hardware component 916,916′, 916″ also includes an SA driver 1016 and a WIDE driver 1064 (seeFIG. 8). Network 914 connects the first hardware component 916 to thesecond hardware component 916′, and network 914′, which is a differentnetwork from network 914, connects the second hardware component 916′ tothe third hardware component 916″. Routing tables comprising theinformation on the structures contained in the memory of the firsthardware component 916 and of the second hardware component 916′ of FIG.32 are used to encapsulate the complete route from the first hardwarecomponent 916 to the third hardware component 916″. This enables amessage to be sent from the first hardware component 916 to the thirdhardware component 916″ without the first hardware component 916 havingknowledge of the route between the second hardware component 916′ andthe third hardware component 916″. The message can be propagated suchthat a first message is sent from the first hardware component 916 tothe second hardware component 916′ while a second message is sent fromthe second hardware component 916′ to the third hardware component 916″.In this manner, the routing information necessary to route the messagefrom the first hardware component 916 to the third hardware component916″ is contained in part within each of the first and second messages.

FIG. 34 exemplifies the relationships between the structural componentswithin an appliance control system. The appliance has at least onecontrol board which is well known in the art. The control board has atleast one processor able to execute software (also known sometimes asfirmware) and control some part of the appliance control systemapparatus. Control is defined to mean the changing of the state of oneof the hardware components to which the processor is attached. Forexample, a valve may be changed from a closed state to an open state.This represents the control of the valve by the processor. The processormay effect this change of state by changing the state of one of its IOPins which is in effective communication with the hardware component orby sending a network message where the network is in effectivecommunication with the hardware component. Effective communicationrefers to the ability to send and receive messages with meaningfulinformation without defining the exact means by which communication isachieved. The software which a processor executes can be broken into aplurality of arbitrary software components. This breakdown has severaladvantages. They include: manageability, readability, portability,re-usability, e.t.c. It is well known in the art of software design tobreak-up software into modules or components for these reasons.

The invention introduces new components to the appliance control systemwhich will enable the appliance control system to be effectively builtfrom re-usable components and to be dynamically configured by a varietyof configuration mechanisms. Further the invention will deliver thebenefit of re-usability and configurability.

Re-Use

It is known in the art that object oriented techniques promote andenable software re-use. A first component enabling re-use is the classlibrary. Class library contains a plurality of class definitions. Aclass definition comprises an interface with a plurality of methoddefinitions and a plurality of field definitions.

Field definitions are named variables which have a known data type. Thevalue of a field definition must be a value corresponding to the field'sdata-type. Example: Field x is an unsigned integer. The value of x canbe a number within the range of 0 to 65535. Field definitions can alsohave a data-type corresponding to another class definition.

A method definition is a function with a name and a description, areturn value, and a set of arguments. Each argument of the method canalso have a name and a description. Each argument can also have adata-type and a set of valid values. The data-type can also be a classdefinition.

Each method definition further comprises executable software which canuse the arguments in conjunction with the executable software so thatthe executable software returns a result and/or executes the behaviorcorresponding to the logic of the executable software and the values ofthe argument received in the set of arguments. A method definition canfurther comprise invocations onto other method definitions of itscontaining class or to method definitions which it has visibility to.The approach to gaining visibility to other classes' methods is known inthe art. The return values from the other method definitions can be usedby the executable software of the first method either to influence thereturn value of the method or to influence the behavior of the logic ofthe executable software.

Preferably, a class definition is confined to a single logical purposeto which the plurality of methods contributes the enablement thereof. Aclass library can be governed independently of the Appliance ControlSystems to which it is applied. Class Library governance includesdeployment, documentation, development, testing, bug fixes, revisioncontrol and the like.

Class definitions are made executable in two ways. The first way is viaa method known as static. When a class is executing statically, allexecutions of the methods of the class are occurring within the samememory of the processor. This means that if there are two executionsoccurring simultaneously, the methods of the class must be designed suchthat any state information used within the execution and stored inmemory by a first execution is guarded against inadvertent use by asecond execution.

Two factors giving rise to the second way are that 1) it is advantageousfor methods to store state information in memory for later use and 2) toenable the 1), it is required to index that state information to aparticular execution or execution context so that when there aremultiple executions or execution contexts that the method can retrievethe appropriate state information.

Therefore, the second way a class definition is made executable is byinstancing a class into an object thereby creating the mechanisms toassign an instance of a class to a particular execution or executioncontext. Instantiation refers to the allocation and assignment of memorysufficient to hold a unique collection of information associated with aunique object instance and defined by the field and method definitionsof the class definition.

Instantiation is the mechanism which allows a class's state informationand references to other objects to be encapsulated together andassociated with a particular execution or execution context and toexpose that instantiated memory to other objects via some type of memorypointer or unique identifier.

An object has the ability to store information associated with itsexecution context and in its fields. When an object has a field of adata-type that corresponds to a class, the value of the field can be anobject. In this way, objects can be composed of their own fields of dataand methods and of a plurality of other objects.

Dynamic Configuration

As previously stated, objects can be composed of a plurality of otherobjects according to the objects field definitions. If an objectcomprises a method which has executable software to set the value of afield defined to hold an object, then that object can be reconfigured bychanging the value of the a field from a first object to a secondobject. This reconfiguration can then result in a different composite oroverall appliance control system behavior. There are many usefulpurposes for an appliance control system whose behavior can be changedby changing the values in a first objects field to a third object from asecond object. For example, a cycle accessory could use this techniqueto change a cycle structure. Likewise, both a consumables reader and arecipe book wand could use these techniques to customize the behavior ofthe appliance control system according to the data about the cycle, thedata about a consumable, and the like.

There are many mechanisms which can initiate and manage the dynamicconfiguration of an appliance control system. However, these mechanisms(see FIG. 34) will need a common design framework with which toaccomplish the dynamic configuration. And some portions of the dynamicconfiguration can be accomplished during the compile process while otherportions may be accomplished at post-compile time (also known asruntime).

FIG. 5 illustrates at least two embodiments of communicationscontrolling the operation of an appliance according to the invention byinformation related to a cycle structure 71. Here, cycle structure 71(a)represents changes to be communicated to the cycle engine 73 (e.g. a newcycle structure or modifications to an existing cycle structure) orinformation about a cycle structure 71, and cycle structure 71(b)represents a cycle structure after change by the cycle engine 73.Messaging (1) communicating a cycle structure 71(a) to the cyclearchitecture 69 enables the cycle engine 73 to discover informationrelated to a cycle structure 71, data about a cycle structure 71, or acycle structure 71(b) to be created or modified. The cycle engine 73proceeds to build a new or modified cycle structure 71(b) at (2).Optionally all messages can be routed through an embedded virtual routerat (3) resulting in the cycle engine 73 using its own configuration APIfor building the new or modified cycle structure 71(b). As well theexecution by the cycle engine 73 to create or modify the cycle structure71(b) can be accomplished through an EVR.

Alternatively, any client having an arbitrary software component, suchas a client 40 in the consumable holder 16, can find or discover thecycle structure or data about a cycle structure 71 at (4). Then, thearbitrary software component can build a new or modified cycle structurein conjunction with the cycle engine 73 configured to receiveconfiguration messages as at (5).

Thus, it is seen that the creator of a new or modified cycle structure71 is the cycle engine 73 or an arbitrary software component incommunication with the cycle architecture 69. The arbitrary softwarecomponent can reside in a variety of locations with respect to thecontroller 68 comprising the cycle architecture 69. See the discussionbelow with respect to FIG. 7. Hence, all messages between the arbitrarysoftware component and the cycle architecture 69 can be optionallyrouted through an EVR as at (6). As well, the cycle architecture 69 canoptionally communicate with the appliance control system through an EVR.

Using the aforementioned cycle engine architecture 69, an operationalcycle accessory can be added to the network of an appliance, discoverthe cycle architecture 69, and send it configuration messages to affectits structure and ultimately its execution. In this case, theoperational cycle accessory would typically include a combination ofsoftware and data to accomplish the configuration of the cyclearchitecture 69. Alternately, the aforementioned cycle architecturemight send a discovery message seeking identification of all sources ofthe cycle structure. Sources of the cycle structure may be in ROM,Flash, EE Prom, an operational cycle component, and/or an externalsource connected via a network different from the control network (See,for example, FIG. 7). Once the cycle structures 71(a) are located andretrieved, the cycle engine 73 can commence modifying its own cyclestructures 71(b) according to the new cycle structure data.

In another embodiment of a cycle architecture 69, a first portion of thecycle structure 71(a) is compiled and a second portion is made availableat runtime. The second portion can include a plurality of cyclestructure data, either in direct or indirect form, which can be combinedwith the first portion such that the cycle engine 73 operates on theaggregate of the first and second portions for a new operational cycleexecution software. The second portion may represent differences in thefirst portion where differences may be additions, deletions, ormodifications to elements, their relative orders, or their relativerelationships within the cycle structure. The cycle engine 73 couldappropriately apply the differences represented in the second portion bylooking at the identifiers of the elements of the first portion of thecycle structure 71(a) and the identifiers of the elements of the secondportion of the cycle structure 71(a). The advantage of this embodimentof a cycle architecture 69 is that changes to the aggregate cyclestructure can be made while preserving the first portion such thatsubsequent corruption or absence of the second portion would not effectthe integrity of the first portion, thus enabling the operation cycleexecution software to revert to compiled default state, such as might besupplied at the factory. A second advantage of this embodiment is thatspecialized variants of the first portion can be designed which canaccommodate the constraints presented by the appliance process controlapparatus 14 and more specifically the controllers 68 such as limitedmemory and also provide capability for receiving and adapting to asecond portion providing flexibility and configurability within theconstraints for the cost of the specialized variants. For appliances,this can be an important requirement in some cases.

Alternatively, when an operation cycle accessory is disconnected fromthe cycle engine 73, the data of the second portion can be optionallyremoved by the cycle engine 73 causing a reversion to the factorydefault state. This is a form of anti-piracy protection in that theoperation cycle accessory must be present for the additionalfunctionality represented by the accessory to be available to theappliance. Optionally, the connection between the appliance and theoperation cycle accessory can include a transfer of the first portioninto a memory in the appliance. In this case, additional operationcycles can be retained without the permanent presence of the operationalcycle accessory. It should also be noted that an operation cycleaccessory can be virtual in that the software and data and ability tocommunicate with the cycle engine may reside on an external deviceconnected to the cycle engine 73 via at least one network and notphysically attached to the containing appliance 12.

It is to be noted that an operational cycle component 60 can have otherelements that are not the aforementioned operation cycles or constituentdata and complied portions. For example, the operational cycle component60 can include software code to configure a cycle engine 73 forcommunication and other functions or code to put software architectureinto an alternate mode for the purpose of diagnostics or changingmemory.

An appliance cycle of operation performed by the appliance processcontrol apparatus 14 can be optimized by information associated with theconsumables 24 on which the appliance process control apparatus isoperating. For example, the cycle structure 71 could be builtspecifically to accommodate some properties or attributes of theconsumable 24 or to accommodate some properties or attributes of theconsumable holder 16. The body or bodies that comprise information,identifiers of functionalities, properties, attributes, and property andattribute values related to consumables 24 can be referred to as sourcesof information about a consumable or “consumable information holders.”Examples of consumable information holders include the consumableitself, a data pod, the consumable holder 16, a user interface, and atag. The consumable holder can be a sensing consumable holder that mightuse a lid sensor, for example, for sensing attributes about theconsumable contained therein. These attributes could then be used by theelectronics 30 to further refine operation of the consumable holder. Forexample, if the consumable holder were to dispense 2 ounces, a lid withan amount sensor could be configured with an analog circuit coupled tothe electronics 30 to provide a level or volume feedback so that theelectronics 30 can dispense exactly 2 ounces rather than a time-basedapproximation.

Information associated with a consumable can include amount and/orcomposition or other attributes that would characterize the magnitude ofthe usefulness of the consumable. In this case, the cycle architecture69 may adapt itself based on the information. For example, if theconsumable 24 were a dishwashing rinse aid and the consumable holder 16had only 90% of the standard dose, the cycle architecture 69 might adaptitself to this condition by increasing the time of the rinse phase tocompensate for the lack of rinse aid. Information associated with aconsumable can also include parameters of an operating cycle such aspersonal preferences of a user (e.g., doneness or crispinesspreferences), and data about the consumable holder 16, the appliance 12,or other accessories or components thereof.

In a laundry example, the appliance process control apparatus 14 mayprovide information to the cycle architecture 69 about process variableslike soil level, load size, soil type, etc. Based on this informationassociated with a consumable, including the process variableinformation, the cycle architecture 69 or an arbitrary softwarecomponent in conjunction with a cycle engine 73 can reconfigure thecycle structure 71 to adapt to the process variable information. Theconsumable holder 16 may comprise the arbitrary software component andbe able to reconfigure the cycle structure 71 to adapt to the processvariable information. As shown in FIG. 5, reconfiguration can beaccomplished in at least two ways. In one way, the arbitrary softwarecomponent can read the cycle structure 71 and communicate with the cycleengine 73. In a second way, arbitrary software component can bepreconfigured and communicate that configuration to or instruct thecycle engine 73 about the configuration.

One example of commands associated with an operating cycle is acollection of key value pairs. Keys comprise parameter names having ameaning, wherein the meaning is known by the cycle engine 73 such thatvalues associated with the keys are thereby associated with themeanings. This enables the values to be used in the contexts of themeanings to modify and/or control the cycle of operation of theappliance.

Another example of commands associated with an operating cycle is a bytearray representing a message packet for a network. In one embodiment ofthis example, the byte array could be arranged according to the packetdefinition disclosed in WO2006135726 comprising a functional identifier,an op code, and a payload, wherein the identifier and op code relate toan executable function or method implemented by the cycle engine and orcycle engine API. Further, the arguments or parameters of the functionor method correspond to the data elements contained in the payload ofthe message packet.

The consumable holder 16, therefore, can contain all the functionalityof and participate in all the embodiments that an operational cycleaccessory in communication with an appliance 12 having a cyclearchitecture 69 can. Therefore in one embodiment, a consumable holder 16is an operation cycle accessory that further physically contains and mayalso further be enabled to directly actuate the introduction of aconsumable 24 into an appliance 12.

Consumable Reader

Looking again at FIG. 1, a consumable reader, such as that representedat 22, is any device capable of retrieving data or informationassociated with a consumable 24 directly from a consumable informationholder (see discussion below) and exchange data concerning theinformation by sending and receiving data. A consumable reader 22 caninform memory in the consumable holder 16 of the type of detergent beingheld therein, for example. The use of this information could effect theoperation of client software held in the consumable holder's optionalclient 40. Example effects could be dispensing quantities, frequency, ortiming as controlled by the optional client software in communicationwith the consumable holder's process control apparatus 28 (having atleast an actuator to control dispensing). Other example effects includecommunications between the optional client 40 and the controller 68 ofthe appliance 12 which could affect the structure and execution of thecycle architecture 69. See the earlier discussion of operational cycles.The optional client 40 will typically comprise electronics including aprocessor able to communicate with the communicating control nodeswithin the appliance process control apparatus 14 and the processcontrol apparatus 28 in the consumable holder 16. The optional client 40in some cases might be an arbitrary software component (as shown in FIG.5) in communication with a consumable reader.

Information associated with a consumable, such as an operating cycle, acycle structure, data about a cycle structure, data that can create orbe interpreted to create a cycle structure, usage directions, cookinginstructions, preparation instructions, dosage information, nutritionalinformation, promotional and sale information, information aboutreplenishment, offers for replenishment, reminders for replenishment,images and messages for user interface screens, and washing/dryinginstructions can persist, for example, within the consumable itself, inthe packaging for the consumable, or in auxiliary materials, such asuser manuals and performance tags, provided with the consumable. Theconsumable reader 22 is a component that can accept the informationassociated with the consumable and transmit it elsewhere, such as to thecontroller 68 of the appliance 12. The consumable reader 22 can be adevice integrated with the appliance 12 or with the consumable holder16, or a separate device that can be coupled, either by a hardwireconnection or wireless connection, to the appliance or consumable holderfor communication. Examples of consumable readers include, but are notlimited to, bar code scanners, radio frequency identification (RFID) tagreaders, imaging systems, cameras, intelligent vision systems, devicescapable of communications using NFC (near field communications), andmagnetic strip readers, enabled to send and receive data.

In another embodiment, an external device such as a phone, PDA,computer, camera, and any external client 1004/1002 able to read anddecode the information from the consumable and communicate theinformation to an appliance is an example of a consumable reader. Inthis embodiment, the device could communicate the information directlyif the device were in communication with the appliance network 1030 orthe device could communicate the information using propagated messageson other networks such as 1052, 1070, or 1050.

The consumable reader 22 communicates the information associated withthe consumable 24 to the appliance 12 so that the appliance can optimizeits performance for the consumable. An example of employing theconsumable 24 and consumable reader 22 is provided in the schematicillustration of FIG. 6. In this example, a food provider 70 determinescooking instructions (a cycle structure 71) for a consumable 24 in theform of a frozen meal 71 and encodes the packaging, which is aconsumable holder 16, for the consumable 72 with the cookinginstructions. A user can place the consumable holder 16 in the vicinityof the appliance 12, which in this instance is an oven, and a consumablereader 22 of the appliance 12 reads the encoded cycle structure 71(cooking instructions) from the consumable holder 16 and communicatesthe cycle structure directly to the appliance 12. The cycle architecture69 in the appliance 12 can then either execute the cycle structure 71for preparing the frozen meal directly, or create a new or modify anexisting cycle structure in the appliance 12 without need for additionalinformation from another source and without need for consumable-relatedlookup tables. The information associated with the consumable can beself-executing.

The aforementioned example should not be limited to a food provider. Anyconsumable provider with an authoring tool should be able to developinformation about a consumable, preferably in a form appropriate for thecreation of an optimum cycle structure 71 and user interaction with theappliance user interface, and encode the information into the consumableor onto the consumable holder so that when the consumable is introducedinto the use environment, the optimum cycle structure and the optimaluser interaction can be created within the cycle architecture 69 so theuser will have an optimum experience. An authoring tool comprises acomputer with appropriate software, a driver 1016, an appliance withsoftware architecture 1018, a network connecting the computer to theappliance for communication, and a data store for storing informationabout a consumable preferably comprising information about a cyclestructure and information for use on a user interface and preferablywith at least one identifier identifying at least one appliance.

It is contemplated that information associated with consumables will beavailable from a data source that contains or can acquire theinformation associated with consumables. The information can include atleast one cycle structure corresponding to a preferred operating cyclefor the consumable 24. In the case of a food item, the cycle structure71 might be used to realize a complete cooking cycle definition for thefood item. In this embodiment, the cooking appliance 12 can comprise atleast one instance of the cycle architecture 69 so that the introductionof the cycle structure 71 into the vicinity of the cooking appliance 12results in the creation or modification of a cycle structure 71, andinitiation of a preferred operating cycle corresponding to theparticular combination of the food item 24, the cooking appliance 12,and other attributes, such as the geographic location the cookingappliance 12 and its altitude. Moreover, the food supplier or anyconsumable or article provider might also encode cycle informationcomprising a sound, graphics, ring tone or other licensable informationenabling the cycle architecture 69 to render the licensable informationvisually or audibly on behalf of the food or consumable provider.

It will be understood that information associated with consumables cancomprise data about a consumable, such as identifiers offunctionalities, properties, attributes, and property and attributevalues that describe or characterize something about a consumable 24 orits consumable holder 16. The data about a consumable can manifestitself in any type of data structure appropriate for useful storage andretrieval. Examples of appropriate data structures are key-value pairs,XML, relational data tables, comma separated variable files, bytearrays, data packets, command objects, serialized objects, messages, andthe like. The data about a consumable may reside entirely within or uponthe sources of information about a consumable or consumable holder aswill be discussed in more detail hereinafter. Alternatively, the dataabout a consumable may be created by a second arbitrary softwarecomponent using a combination of a cycle structure 71 and informationassociated with consumables. In either case, the data about a consumableis constructed from information associated with a consumable orconsumable holder retrieved from a source of information about aconsumable or consumable holder.

Information associated with consumables can also comprise userpreferences to further refine the creation or modification of the cyclestructure 71 to correspond to the preference of the user of the cookingappliance 12. The consumable 24 and/or consumable holder 16 can also beenabled to identify the appliance 12 and provide an appliance-specificoperating cycle. One manner of implementing this is for the consumable24 and/or consumable holder 16 to have operating cycles corresponding toa particular appliance or class of appliance 12. The appliance 12 inwhich the consumable 24 and/or consumable holder 16 is used identifiesand implements the relevant operating cycle. Another manner ofimplementation is for the consumable 24 and/or consumable holder 16 tohave an identifier, and the appliance 12 has stored or access to adatabase or table of operating cycles for different consumables 24and/or consumable holders 16. The appliance 12 takes the consumableidentifier and looks up the corresponding operating cycle for theconsumable.

Information associated with consumables can be in any suitable form. Inone embodiment, the information can be a communication packet that canbe directly transmitted to the software architecture 1018, therebyeliminating a need for a central storage of consumables data. In anotherembodiment, the information can be a key that can be used to direct theappliance 12 to stored consumables data.

The consumables 24 can be supplied by a third-party provider, as in thecase of store-bought frozen meals and wash aids for laundry appliancesand/or dishwashers, or provided by the user. Leftovers and cooked anduncooked prepared foods are examples of consumables 24 that can beprovided by the user. The leftovers and the prepared foods can be placedin a storage container (consumable holder 16) encoded with informationrelated to the leftovers and prepared foods. For example, theinformation can include re-heat or cooking instructions and anexpiration date (i.e., throw away date). When the information includesthe expiration date, the appliance 12, such as the oven or microwaveoven, can refuse to re-heat or cook the food if the current date is pastthe expiration date. Optionally, the appliance 12 can be configured toreceive an override command from the user when the user desires tore-heat or cook the food despite the expiration date.

Any suitable material can be used to encode the information, andexamples include, but are not limited to, plastic wrap, aluminum foil,pots, pans, microwave-safe containers, container lids, and an adhesiveor magnetic strip that can be placed on the storage container. Theinformation can be configured by the person who originally prepared theleftovers and the prepared foods and encoded using any suitable means,such as a personal computer, a magnetic strip writer, or a handheldencoding device. With this configuration, the user can configure theinformation on the consumable 24 as desired. In this manner, theconsumable holder 16 facilitates the acquisition of the data associatedwith consumables 24 from a data source.

Taxonomy

A taxonomy architecture is employed to avoid duplication of softwarelogic (sometimes called business logic) between two interacting softwarecomponents in a controlling device and a controlled appliance. It isbeneficial when the controlling device is a consumable holder. Inparticular taxonomy permits a command generator in a controlling deviceto readily control an appliance without any information about theappliance being controlled except the control taxonomy itself. This canincrease the flexibility of introducing “generic” control devices tocontrol new appliances, adapting control devices to newly availablecycles or functionalities which have been added to an appliance, andswitching appliances between modes of operation where differentoperating cycles or functionalities are available. It also makes controlof appliances easier for users since they need only be presented withchoices which are currently available from the appliance.

A structured taxonomy dataset can efficiently communicate to thecontrolling device, e.g. a consumable holder, just that informationwhich the controlling device needs in order to generate a well formedcommand for the appliance or other device such as a user interface. Asused herein, a well formed command is a command which has meaning and isperformable by the appliance or other device such as a user interface.The information conveyed by the dataset includes a hierarchy of optionsand data inputs required to form the well formed command. In oneembodiment, it also includes semantic or contextual information tocommunicate in word or iconic form the available options so that a usercan understand the available choices and enter the appropriate data.This is preferably accomplished by labels within the dataset that areassociated with arbitrary or non-user friendly identification elements.This allows the logic of the software componentry which must interpretand process the Taxonomy to be decoupled from the presentation of theTaxonomy on a user interface.

Referring now to the FIG. 23, generally, the appliance 12 beingcontrolled has a software component 816B having an appliance controllerand a status generator. The controlling device 816, 822 (e.g., theconsumable holder, consumable reader, or other client) used to controlthe appliance has a software component 816B with a command generator, aselection builder and a status interpreter. The controlling device 816,822 may be a programmable user interface such as a PDA, web tablet, acell phone, an LCD attached to the appliance or a client device.

The taxonomy architecture, shown disposed in the appliance controller816 and logic, can be disposed in a remote location, such as in acontrolling device or on the internet. The taxonomy architectureincludes a taxonomy generator, a taxonomy engine, a taxonomy translatorand a taxonomy structure. The taxonomy architecture generates a taxonomydataset defining taxonomy capabilities facilitating the creation, by thesoftware component 1 816B, of well formed commands that can be executedby software component 2 816B. Each of these components and theirinterrelationships are described in greater detail below.

Creation of the Taxonomy Dataset

The taxonomy dataset is derived from the operational capabilities of theappliance controller 816 structured in a manner to allow the commandgenerator in the software component 1 to interpret the dataset toaccomplish several results. More particularly, from time to time thetaxonomy engine uses the taxonomy structure and the state awareinformation to generate a taxonomy dataset reflective of the subset ofthe universe of options for commands that would be available from anappliance to those that are currently available from the appliance.

For example, the taxonomy dataset describes the available functionssupported by a software component 16B, each functions argument, and thevalid values of each argument in a data structure. In addition, taxonomydataset defines the valid values of feedback variables. Since this in adata structure, it can be transmitted and re-transmitted to clients 816or 822 as required. Changes to taxonomy dataset occur as the cycles ofoperation progress and the available commands or the valid values oftheir arguments change. Moreover, additional commands may becomeavailable or may become invalid as a cycle of operation progresses.

More particularly, the selection builder registers with the taxonomymanager to receive notifications for new taxonomy engines. In response,the taxonomy manager passes references to all known taxonomy enginesback to the selection builder. The selection builder then requests fromeach taxonomy engine a taxonomy capabilities data set. The taxonomyengine evaluates a taxonomy structure comprised by the controller logicof software component 2 or alternatively a document to generate ataxonomy capabilities dataset. The selection builder then populates aset of pseudo command structures appropriate for an application endpoint (examples of application end points are user interfaces forcontrol or service or other intermediate application layers like anenergy controller or home automation mode like vacation or goodnight.)and passes those structures to the application end point allowing theapplication end point to be configured. Alternatively, the selectionbuilder may directly configure the application end point.

Communication and Use of the Dataset.

When a controlling device is networked with the appliance, the taxonomymanager establishes a relationship between the software component 1 andthe taxonomy architecture allowing the command generator to query forthe existence of taxonomy datasets, providing the software component 1access to a taxonomy dataset, and allowing the command generator andstatus interpreter to subscribe to taxonomy dataset updates. Thetaxonomy translator is an optional component that translates thetaxonomy datasets between software components 1 and 2.

The taxonomy dataset is communicated to the controller of softwarecomponent 2 and to the selection builder of software component 1.Optionally, the taxonomy translator translates the taxonomy dataset to adifferent schematic definition of the command generator.

The command generator uses the taxonomy dataset to construct andpopulate a set commands structures available for selection by a userinterface or other client applications comprising a set of validcommands, their valid arguments, and each arguments valid values. Moreparticularly, the command generator uses the taxonomy dataset toconstruct one or more well formed commands which can then be transmittedto the controller. Since the taxonomy dataset can be reset and sent atdifferent times by the taxonomy engine, or the dataset can be updated byrevisions from the taxonomy engine, the command generator can have acurrent set of command structures then available for selection by a userinterface or other client application.

Thus, in essence, through use of the taxonomy architecture, the softwarecomponent 2 or its proxy (the taxonomy translator) communicates tosoftware component 1 a rule set that can be interpreted by softwarecomponent 1 so that software component 1 does not request something ofsoftware component 2 which software component 2 cannot accommodate anddoes not operate on a state variable which is set to an invalid value.

Before the application end point is able to commence execution, it willrequest or register for status updates with a Status Interpreter. Thiswill allow the application end point to be populated with valid statevariables from the controller before logic is executed and before userinterface componentry is rendered. The status interpreter will processtaxonomically correct status datasets and validate those datasetsagainst the taxonomy capabilities data set. The status interpreterrequest or register for status updates from the status generator ofsoftware component 2 via the taxonomy engine. Upon receipt of ataxonomically correct status, the status interpreter will provide newstatus values to the application end point.

The application end point executes resulting in a rendering of thecurrent status of software component 2 and a rendering of selectablepseudo command structures. Each time a selection is made from the pseudocommand structure, the selection builder populates a set of validsub-commands appropriate for the selection for further selection by theapplication end point. When a complete selection is made, a structurecontaining all pseudo commands are passed to the command generator.

The command generator will construct a taxonomically correct well formedcommand and optionally via the taxonomy translator, invoke the commandonto the controller of software component 2 via the taxonomy engine.

Execution

The well formed command is delivered to the controller of the applianceand executed by the appliance.

Typically, the command will result in a state change to the associatedmemory of software component 2 which will trigger a status updatecreated by the status generator and resulting in new renderings of stateto the application end point. This change in state will result in a newcapabilities taxonomy or a partial capabilities taxonomy which canreplace portions of the original capabilities taxonomy. The newcapabilities taxonomy resulting in a different set of valid selectionsfor controlling the cycles of operation of software component 2.

Validation

The status interpreter uses the taxonomy dataset to validate statusupdates from the controller or taxonomy translator. The dataset containsinformation structured in such a way to allow the controller to fullyvalidate incoming commands according the structure without additionallogic outside of the dataset. For example, the dataset can beconceptually thought of as one or multiple decision trees, with eachlevel of the taxonomy forming a different decision branch, with each ofthe options and/or data inputs can form a different level. The keypresses on the user interface required to select the options and/or datainputs in forming the well formed command can be compared against thedecision tree to confirm that each key press is found within a commonbranch on the decision tree. If the key presses are not found, then itis an indication that the command contains an error. The taxonomystructure thus serves to populate the user interface with availableoptions and data inputs for a given state of the appliance and alsoserve as the logic for validating the resulting command.

The taxonomy dataset can be thought of as all available options andsettings for an appliance at the current state. For example, theappliance comprises multiple components interconnected by the internalnetwork. Each of the components can have one or more devices. Each ofthe devices has one or more functionalities, which has one or moresettings. All of the functionalities for all of the devices will notnecessarily be available during each state of the appliance. As such,the taxonomy dataset will comprise all options and data inputs for alldevices that are currently available.

Consider a microwave oven with a top level of the hierarchy showing theoptions of COOK, JET DEFROST, BAKED POTATO, STEAM COOK, AUTO REHEAT, ANDDINNER PLATE, as illustrative examples. The user must select one of theoptions from the top level.

A detailed example of the creation of the taxonomy dataset and the wellformed command should prove useful. The creation of the taxonomy datasetfor the microwave with multiple cooking cycles was constructed by thevisual configuration utility (see FIG. 27) from the taxonomycapabilities dataset as is illustrated in XML as follows:

<device id=″microwave″ label=″Microwave Oven″> <device id=″ovenCavity″label=″Microwave Oven″>  <char name=″cycle″ label=″Cycle″default=″timedCook″>  <setting name=″timedCook″ label=″COOK″ />  <charname=″turntable″ label=″Turntable″  default=″on″> <setting name=″on″label=″ON″ /> <setting name=″off″ label=″OFF″ />  </char> <rangename=″duration″ label=″Duration″ default=″30″ units=″seconds″ max=″6039″min=″60″ inc=″1″ /> <range name=″power″ label=″Power Level″default=″100″ units=″%″ max=″100″min=″50″ inc=″10″ /> </setting><setting name=”jetdefrost” label=”Jet Defrost”/> <char name =foodTypelabel =”Food Type”/> <setting name=″poultry″ label=″POULTRY″ /> <setting name=″meat″ label=″MEAT″ />  <setting name=″fish″ label=″FISH″/> </char> </setting> | | | etc  </char> </device>  </device>

If the user of the microwave chooses to Cook for 30 seconds at 90% powerwith the Turntable On, a well formed command of the taxonomy datasetwould be transmitted optionally to the Taxonomy Translator and to theTaxonomy. The command would be of the form:

<command id=“ microwave ”>  <device id=“ovenCavity”> <sequence> <stepid=“21”> <char name=“cycle” setting=“bake”/> <char name=“power”setting=“90”/> <char name=“duration” setting=“30”/> <charname=“turntable” setting=“on”/> </step> <step id=“22”> <charname=“power” setting=“70”/> <char name=“duration” setting=“40”/> <charname=“turntable” setting=“off”/> </step> </sequence>  </device></command>

The taxonomy engine would then traverse the taxonomy structure totransform the well formed command of the taxonomy dataset to a wellformed command of the controller of software component 2 of a packetstructure 828. The taxonomy structure is a superset of the taxonomycapabilities dataset. For each specifiable command element above (e.g.,cycle, power, duration, and turntable) an additional collection of keywords and values necessary to form payload 828A would be associatedwithin the taxonomy structure. These key words would include API ID, OpCode, and Position Index into the payload 828A where position indexcould be a byte offset or a bit offset.

The taxonomy dataset could be constructed to directly represent theuniverse of possible commands of the APIs of software architecture 10providing useful functionality for a service, factory, or laboratoryengineer or technician.

It will be understood that the structure illustrated in FIG. 23 is moreconceptual than physical. FIGS. 24 and 25 show embodiments of thetaxonomy architecture of FIG. 23, partitioned according to the physicalarchitecture of an appliance or an appliance network.

The software component 1 (816B in FIG. 23) is represented as beingwithin a remote client 822, such as a remote controller with a userinterface. Consequently, the sub-components of software component 1 816B(the selection builder, the command generator, and the statusinterpreter) are specialized for this user interface application. FIG.24 shows software component 1 in such a user interface device,identified here as a “thick client.” A thick client would have theability to parse a data structure such as an XML document, interpret itsmeaning, and implement the ‘Selection Builder’ functionality. Softwarecomponent 2 and the taxonomy architecture reside in the appliance 12.

FIG. 25 depicts a second embodiment of the taxonomy control architecturewhere all components are included within an appliance 12. In thestructure of FIG. 25 the taxonomy architecture uses a taxonomytranslator (not necessary in the embodiment of FIG. 24), therebyrendering the status interpreter of software component 1 to the reducedfunctionality of an input handler. The UI board in this case comprisesan “a” side and a “b” side, each with is own processor. Both sides areconnected to each other, preferably by a serial communication “c”. TheUI board is connected by another connection 814 to a CCU with softwarecomponent 2, where the connection 814 can be the same type as connection“c”, or it can be different. The “a” side is preferably an LCDcontroller that exposes a low level API, and lacks the full capabilitiesof a thick client. Hence, the “a” side can be referred to as a “thinclient.” The “b” side comprises the taxonomy architecture and softwarecomponent 1.

FIG. 26 is a more generalized block diagram of the architecture of FIG.23 with elements rearranged for clarity and to show a less specializedconfiguration. In FIG. 26 a, it can be seen that The taxonomy enginecomprises a taxonomy controller, a model, and a collection of operators.The taxonomy controller is aware of the state of the componentry forwhich it is controlling, and is responsible to retrieve from thetaxonomy structure the state appropriate taxonomy model and inform thetaxonomy engine of the change. This action provides an event to theappropriate taxonomy operator to examine the new taxonomy model andgenerate a new taxonomy capabilities data set. The taxonomy engine thenpublishes the new capabilities to the taxonomy manager, who thendistributes the new information to the appropriate translators or othersoftware components that have registered for notification.

It will be apparent from FIG. 26 that the selection builder, the statusinterpreter, and the command generator found in the software component 1of FIG. 23 is now in the taxonomy translator. Taxonomy translator 2comprises the selection builder and is responsible for the conversion oftaxonomy datasets to software component specific interfaces. Therefore,in this example the software components are not comprised with thefunctionality of interpretation or generation of taxonomy datasets.Rather, they are comprised with handling inputs from the translator andsending outputs to the translator.

It is contemplated that a taxonomy architecture, through the use ofmultiple translators, can simultaneously connect to software componentssimilar to software component 1 of FIG. 23 and software component 2 ofFIG. 26.

Looking now at FIG. 27, it is generally known that complex datastructures have tremendous advantages because they can be easily variedand re-used with a single complied source code. But this complexity canbe troublesome to understand, create, troubleshoot, debug, explain, andgenerally manage. Object oriented languages provide some level of hidingcomplexity relative to non-object oriented languages such as C.Similarly, XML data structures are human-readable, in contrast to bytearrays, and therefore can eliminate complexity. But it is currently costprohibitive to implement technology such as XML or Java in mostappliances for domestic use. The invention offers a visual configurationutility that simplifies handling complex data structures at much lesscost than known systems.

Following the flow of FIG. 27, a designer in step 1 starts the visualconfiguration utility. A designer can be someone who does the role ofproduct or feature planning, user experience, or user interface design,engineering, or anyone else with a need to retrieve value from orprovide value to the information contained by an instance of aconfiguration held within the memory of the visual configurationutility. In step 2, the designer uses the configuration utility. In thisstep, the design will load a configuration file from a persistent storesuch as a hard drive or database or web site. Alternatively, it may bechecked out from a document version control system such as visual sourcesave.

In step 3, the designer creates a new configuration comprising ataxonomy structure or begins editing an existing configurationcomprising a taxonomy structure. The editing process includes steps likeadding new taxonomy elements, deleting taxonomy elements, movingtaxonomy elements, or modifying the properties of a taxonomy element.Other sub-steps of step 3 may include binding taxonomy elements tomessage identifiers or functional identifiers of arbitrary softwarecomponents of which taxonomy elements either relate to or represent. Instep 4, the designer will save the taxonomy configuration appropriatelyand notify the appropriate office mates such that if one of the officemates is the appropriate controls development engineer, he mayimmediately acquire the saved taxonomy configuration file and begin step5. In step 5, an appliance controls development engineer will generate asoftware and software data file appropriately configured such that acompiler can be invoked preferably from the Visual Configuration Utilityto create a downloadable image appropriate for execution by a processor.Further, the controls development engineer will combine the generatedsoftware and software data file with a plurality of other arbitrarysoftware components. Preferably, the Visual Configuration Utility canaccomplish this task. In step 6, the appliance controls developmentengineer will invoke the compiler on the combined file and the compilerwill generate a downloadable image. And in step 7, the appliancecontrols development engineer will download the downloadable image tothe embedded appliance control processor and test the result. At anystep in the process, the process actor may stop activities and moveanother step taking appropriate action to mitigate the incomplete stepand/or the potential re-ordering of steps.

FIGS. 28 and 29 depict an application built using a proprietaryapplication framework. The taxonomy visual configurator of FIG. 28 wouldbe used as a rule set to develop taxonomy structures. Once the taxonomystructure is configured visually, it can be transformed and exportedinto a functionally equivalent complex embedded data structure. (Seestep 3 of FIG. 27) Note how the taxonomy structure comprises multipletaxonomy structures, each associated with a unique appliance state.Examples of unique appliance states are found in FIG. 7.

Looking more closely at the example of FIG. 28, it can be seen thatthere is no wash phase definition. This is because wash phase is not avalid feedback until the appliance is in running state. In FIG. 29,there is no cycle definition. This is because during running, the cycledefinition cannot be changed.

The data structure of FIGS. 28 and 29 is very powerful and is the heartof the taxonomy architecture. It consists of a nested tree of elementswhere each element of the tree has a type where that type dictates tothe taxonomy operators of FIG. 26 how to properly traverse and extractinformation from the Tree. Attributes should have corresponding ActiveValues which are one of the child Values of the plurality of childValues. Attributes contain a plurality of child Values which representthe valid selections of the Attribute. A Value which contains aplurality of Attributes is a Value which must be further specified byhaving each contained Attribute be defined by its contained active orselected Value. When a child Value is selected or active, the taxonomyoperator looks to see if the child Value contains children of theAttribute Type. If so, the taxonomy operator continues the treetraversal repeating the function of the taxonomy operator on the nextlevel of the tree. Ranges are children of Attributes and are equivalentto a plurality of Values which can be mathematically derived from thevalues of Min, Max, and Inc.

The information contained in the data structures of FIGS. 28 and 29 istherefore more useful than one would at first realize. For example,taxonomy operators can be written to do a variety of useful functionsacross a number of the elements of the taxonomy architecture, especiallywhen there is a graphical user interface or an external client. A firsttaxonomy operator could use the data structure to determine what contentshould appear on a user interface. As a user makes selections on theuser interface, the first taxonomy operator could re-examine the currentactive selections of the user and repopulate the user interface with thenew valid user selections and the valid options of each. A secondtaxonomy operator could be informed of changes to the appliance state.Upon change to the state of an appliance, the second taxonomy operatorcould retrieve a new taxonomy capabilities dataset so that the userinterface could be repopulated based on the new valid selections and ornew valid operators for each. A third taxonomy operator can beconfigured to receive taxonomically correct inputs and check to see thatthe input corresponds to a valid well-formed command. The third taxonomyoperator would accomplish this by walking the taxonomy structure in thetaxonomy architecture of FIG. 26. The third taxonomy operator wouldevaluate all of the potential roots of the taxonomy structure and find acorresponding root identifier in the taxonomically correct inputstructure. From the root, the third taxonomy operator would begin torecourse down the tree, determining which branches of the tree tocontinue down by finding a corresponding identifier in the taxonomicallycorrect input structure. When the third taxonomy operator reaches theend of the tree or alternatively exhausts the elements in thetaxonomically correct input structure having used all of them at leastonce, a valid taxonomically correct input structure is determined ifboth there are no other un-accounted for elements in the taxonomicallycorrect input structure, and there are no child elements remainingun-walked in the taxonomy data structure. This third operation is theequivalent of portable state-based business logic enabling the thinclient 22 of FIG. 24 to be completely devoid of any logic associatedwith the operation of the appliance. The benefit of this is that userinterfaces and all external clients with proper communication andtaxonomy dataset interpretation operators can be developed with onlyknowledge of how to interoperate with taxonomy datasets, and thereforecan be devoid of all knowledge of the connected device with which it isin operable communication.

With further consideration of a consumable holder introduced to anappliance having a service interface, the consumable holder couldcomprise, in addition to data about a cycle structure and data aboutitself and data about a consumable, a new taxonomy structurerepresenting an incremental change to the appliance taxonomy structureor reflecting a new net per state operational capabilities of theappliance and/or the consumable holder. Additionally, the incrementalchange and the new net per state operational capabilities could affectthe user interface of the appliance in response to a new taxonomycapabilities dataset at the user interface. The new taxonomycapabilities dataset is a subset of the new taxonomy structure. Examplechanges appearing in the user interface include new default attributevalues, new cycles, new options, changes to cycles, changes to options,the selectable and non selectable valid values thereof, etc.

A plurality of well formed commands can be derived from a taxonomydataset derived from the operational capabilities of an appliance. Inthis case, the taxonomy structure of FIGS. 27-29 could be created by anauthoring tool such as a visual configuration utility shown in FIGS.27-29 and provided as a data source to the consumable provider so thatthe consumable provider could extract a plurality of well formedcommands for associating with the consumable and/or article such that aconsumable information holder could provide the plurality of well formedcommands to the cycle architecture 69 contemporaneous with itsintroduction into the use environment so that the cycle of operation ofthe appliance 12 and the user interaction with the appliance 12 throughthe user interface such as one shown in FIG. 7 item 110 can be effectedby the commands.

User Interface

FIG. 7 shows a user interface 110 that can be used with the consumableholder 16 according to the invention. The user interface 110 is a userinterface that can communicate with one or more appliances 12.Preferably, the user interface is a graphical user interface or GUI. Theuser interface 110 can be integral to an appliance 12, or the userinterface 110 can be positioned remotely from the appliances 12, such asis illustrated in FIG. 7. For example, the user interface 110 can bepositioned in a central location in the home or can be portable withinthe home. The user interface can provide many, if not all, of thefunctions associated with a traditional user interface of the appliance12 and can include additional functionalities. The user interface 110can have any suitable form, such as a monitor, including a touch panelmonitor. Other examples of the user interface 110 can include, but arenot limited, to a remote keypad, a phone, a personal computer, a voicerecognition device, a voice generation device, a sound generation andrecognition device, a remote control, a user interface of a homeautomation system, a user interface of a component different from thecomponents of the appliance, a television, a device that plays recordedmusic, a device that plays recorded video, and a personal digitalassistant. According to one embodiment, the user interface 110 can beemployed in addition to the traditional user interfaces on theappliances associated with the remote user interface. Alternatively, theappliances associated with the user interface 110 do not include aseparate user interface that physically resides on the appliances.Furthermore, the user interface 110 can be used in conjunction with theabove-described combination appliance/home automation system.

The user interface can be a source of information associated with aconsumable 24, including information about or consumable holder 16 orabout an article with consumable holder capabilities. As discussedpreviously, the appliance 12 can include sensing, meta-data, discoveryprotocols, databases and the like and any combination thereof and otherforms of identification of information associated with a consumable 24,a consumable holder 16, or an article with consumable holdercapabilities. The appliance 12 can also enable the user to manuallyinput information associated with a consumable 24, including data abouta consumable 24 or a consumable holder 16. In this case, the GUI promptsor the user navigates to a screen to input information about aconsumable 24 or consumable holder 16 or an article with consumableholder capabilities. This could be in the form of questions that theuser answers. For example, the GUI might show the user pictures ofconsumables, consumable holders, cartridges, bulk dispensers and thelike and have them select the appropriate picture. This selection wouldthen be translated into information about a consumable or consumableholder. In a second example, the GUI would provide a form to fill outwith standard drop down boxes, radio buttons, text input fields, and thelike so that the user could fully construct and input the informationabout a consumable or consumable holder into the GUI.

Information associated with consumables can be displayed on a userinterface that is operably connected to the network. Further, a userinterface 110 can send a first network message, resulting in a networkmessage on the network being received by a consumable holder 16. Thenetwork message can be the first network message or a second networkmessage in response to the first network message wherein the networkmessage can effect the configuration, enablement, functionality, oroperation of the consumable holder 16 or the appliance 12. In oneexample of information received by a user interface effecting thefunctionality of a consumable holder 16, shown in FIG. 15, the userenters, in message 8, the chemistry option selection and in message 6the user enters the cycle options. In message 17 and 18, the consumableholder determines the dispensing amount using the chemistry optionselection. In a second example, an arbitrary software component residingin the consumable holder might require user credentials to authenticatethe user whereby the authentication may be a pre-requisite to theenablement of the consumable holder 16. In a third example where aconsumable holder 16 is also functioning as a smart coupler as shown inFIG. 8, 1042 a user interface could receive network configurationinformation such as a node id from a user enabling the smart coupler1042 to participate on network 1070.

A user interface 110 can also play a role in the linking of userpreference data to the data associated with the combination ofoperational cycles and appliances so that the user can create or modifyoperational cycle data, optionally associate the data with at least oneappliance, and link the data to user preference data. An example of userpreference data would be a name like “Maria's Cookie Recipe.”, “Sarah'sBrownies”, or “Williams Beef Stew”. The preference data can be storedand an identifier linking the preference data to at least oneoperational cycle and to at least one combination of operational cycleand an associated appliance. Subsequent to the storage, the userinterface 110 can display the user preference data for selection by auser or remember the preference data for subsequent use and infer theselection of preference data via user recognition.

Additionally, a user interface acting as an external client 1004, 1002(see FIG. 8) can connect to a consumable reader and send informationabout a consumable to any appliance on an appliance network as shown inFIG. 8 for the purposes previously explained. In this way, the cost ofthe consumable reader is spread over the appliances on the network.Alternatively, any appliance with a consumable reader and an optionalLCD screen could send information about consumables or information aboutcycle structures to other appliances on an appliance network. Discoveryand Propagated messages can be used to associate appliances on a networkwith the appliance having a consumable reader. Likewise, an appliancehaving an LCD screen could receive information allowing the association.In this way, a first appliance could send to a second applianceinformation associated with a consumable to effect a cycle of operationof the second appliance.

Further, a user interface in communication with a source of informationabout a consumable, e.g. a consumable holder, performance tag, or datapod, could display messages from the consumable. Messages could comprisewarnings such as static warnings included with the source of informationabout a consumable and dynamic warnings based on other information, suchas information about an appliance, information reported by an appliancecycle of operation, a user, a user selection, and the use environment,or information associated with a consumable. For example, a warningcould be that too much detergent was introduced into the wash for thecycle selections of small loads and delicate fabric. This kind ofwarning could be generated by the consumable holder or the othercontrollers 68 and displayed on the user interface and sent as a networkmessage to any node in communication with the consumable holder orappliance.

The user interface can be configured to render multi-media informationin its communication of information to the user. Such multi-mediainformation includes representations other than text. Examples of multimedia information include sound clips, ring tones, songs, images,pictures, graphics, video clips, animations, office documents,PowerPoint slides, stylized text, boldness, size, and color, lines,shapes, symbols, and clip art.

User Instructions about a Cycle Structure in a Consumable InformationHolder

Consumers want superior performance from their appliances. Superiorperformance is often judged according to the condition of article onwhich the appliance cycle of operation operates during or after thecycle of operation. Appliance performance, as perceived by the user, canbe drastically affected by steps the user may take to adequately preparethe article for the cycle of operation, steps the user may take tohandle the article during the cycle of operation, and steps the user maytake once the cycle of operation is complete. These steps can includeactivities associated with any combination of the article, one or moreconsumables, one or more appliances, one or more appliance accessories,one or more consumable holders, and the configuration of one or morearbitrary software components. Examples of preparation steps includepre-wash for dishes, pre-treatment for clothes stains, defrosting frozenfoods, applying ingredients like spices, oils, or condiments to food,shaking a liquid additive like a turkey baste solution, boiling a pot ofwater, removing a food item from a package and placing it in amicro-wave sleeve, mixing an egg with the contents of a box, checkinginventory of needed ingredients, ordering ingredients, shopping foringredients pushing certain buttons, making a selection on a userinterface, rearranging articles in the appliance, checking theappliance, and the like. Examples of handling steps during a cycle ofoperation include removing the article from the appliance for stirring,turning, flipping, applying ingredients like spices, oils, orcondiments, and the like, adding a consumable or ingredient to theappliance, pushing certain buttons, making a selection on a userinterface, rearranging articles in the appliance, closing and openingdoors or lids, and the like. Examples of steps to be taken after thecycle of operation is complete include cooling, applying ingredientslike spices, oils, frostings or condiments, mixing with otherfoodstuffs, hanging up, hanging out, ironing, folding, initiating newpreparation steps for another cycle of operation of an appliance for thearticle, consuming the article, arranging the article, drying thearticle, appropriately storing the article or preserving the article (asin refrigerating or freezing within an appropriate container for anappropriate amount of time), examining the article, replacing thearticle, replenishing the article or purchasing a new article,replenishing, ordering, or purchasing the consumables used inassociation with the article, subscribing to subscriptions associatedwith the article or the consumables used in association with thearticle, pushing certain buttons, making a selection on a userinterface, rearranging articles in the appliance, cleaning surfaces, andthe like.

If accurate information could be readily available which would properlyinstruct the user as to the proper steps of preparation, handling, andpost handling (steps after the cycle of operation is complete) to takein accordance with the article or the use of at least one consumablewith an article and could be practically conveyed to the user, perceivedperformance could be drastically improved.

Presently, accurate information, if it exists, must be read by the userfrom printed instructions on such things as boxes, tags, books, and theinternet.

A consumable information holder associated with any of a consumable, aconsumable holder, an article, or an article holder could comprise dataassociated with proper steps of preparation, regulation, and postregulation (steps after the cycle of operation is complete) to take inaccordance with the article or the use of at least one consumable withan article. The data could be practically rendered on a user interfacein communication with the consumable information holder. An articlecould have more than one consumable information holder, and multiplearticles, each having one or more consumable information holders, can beoperated on by an appliance at the same time. A device such asconsumable reader can perceive the information from the consumableinformation holders and render the information to a user interface. Theuser interface can be interactive so that the user can be guided by theuser interface to perform an ordered collection of steps comprising oneor more preparation steps, handling steps and post handling steps. On aninteractive user interface, the user can enter data affecting theordered collection, including acknowledgement of the completion ofsteps, changing steps, actions and transition conditions in a cycle ofoperation, seeking help, asking inquiries, and the like.

Credentials

The software architecture 1018 can be configured such that theconsumable 24 or consumable holder 16 must present electroniccredentials (i.e., authentication) before communicating with theappliance 12. Requiring electronic credentials prevents unauthorizedcommunication between the consumable 24 or consumable holder 16 and theappliance 12, thereby avoiding undesirable control of the appliance 12by the consumable 24 or consumable holder 16. The security techniquesdisclosed by incorporated WO2006135726, including a firewall, work wellfor the software architecture 1018. Other possible authenticationmechanisms can be used to gain access through the firewall. These caninclude but are not limited to a hardware signal, a sequence ofmessages, a handshaking algorithm, or a standard encryption algorithm.Any standard authentication method can be used to gain access tocommunication capabilities, as long as it is possible to verify that aparticular consumable 24 or consumable holder 16 is authorized to gainaccess.

In addition, the disclosed three basic levels of access to the firewall(access, deny, and temporary access) can be expanded as necessary toenable different levels of access to different consumables 24 andconsumable holders 16. These access levels can each have a uniqueauthentication, such as a unique password, and can be associated withdifferent user roles. Different user roles can include but are notlimited to a service technician, factory tester, developer, or consumer.Different levels of access allow different sets of commands to beexecuted or prompted by the consumable 24 or consumable holder 16. Theselevels can be temporary and time bound, or permanent once authenticationis successfully completed.

The implementation of the firewall can vary as needed. The disclosedimplementation uses a table of protected commands to validate againstdifferent clients, including consumables 24 and consumable holder 16.Any number of data structures can be used to validate a user with theallowed commands for an access level of the firewall. In the end, afirewall must only allow access to commands to the appropriate clientsthat have successfully been authenticated.

Smart Couplers

FIG. 8 illustrates an appliance 1000 similar to appliance 12 connectedto external clients 1002, 1004 and a second appliance 1006, which isalso similar to appliance 12, by a plurality of networks. A firstnetwork 1030 comprises a first internal client 1010, a second internalclient 1012 and the external client 1002. A second network 1050comprises the external client 1004. And a third network 1052 comprisesthe second appliance 1006. Each client is characterized as a node on therespective network. Local clients are clients that communicate withnodes on the same network. Remote clients are clients not directlycoupled to the same network as the node to which they are communicating.In this embodiment, external client 1004 would be a remote client of thenodes on the first network 1030, such as client 40 in a consumableholder 16.

Each client node 1002, 1004, 1010, 1012 comprises a softwarearchitecture driver (SA driver) 1016 for exchanging messages with anynode having a software architecture (SA) 1018, which is similar tosoftware architecture 1018, thereon. The nodes on any given network arein operable communication with the other nodes in that network and areoptionally in communication with the nodes present on other networks.

The appliance 1000 further comprises at least one node 1020 having theSA thereon. The second appliance 1006 will also likely have a node withthe SA on it, and may have one or more clients as well. The firstnetwork 1030 also comprises the node 1020.

Couplers 1040, 1042 are special devices that connect to the applianceand/or to a network and/or to two or more networks and communicatetherebetween. Each coupler can comprise all the functionality of a node,and each node can comprise all of the functionality of a coupler. Inthis embodiment, the coupler 1040 couples the second network 1050 to thethird network 1052, and can function as a node on each network. Thecoupler 1042 couples the second network 1050 to the first network 1030.It could also be considered as coupled to the appliance 1000.

Either of the couplers 1040, 1042 can propagate discovery messagesissued by the SA or an SA driver across the networks in order to enablethe SA and SA drivers or their coupled arbitrary software components todevelop references to identifiers of functionality for the differentnodes. Each coupler 1040, 1042 can have a routing table stored in amemory for enabling communication between nodes on different networks.The memory can also store identifiers identifying the functionality ofeach node. The identifiers can be linked to the routing information heldwithin the routing tables so that when a message comprising anidentifier is sent to either of the couplers 1040, 1042, the couplerreceiving the message can send the message to the appropriate next node.

Each node can comprise a unique combination of software elements. Thesoftware elements on any given node include at least one of the SA andan SA driver. The SA driver enables a node to communicate with the SA.The SA inherently includes an SA driver or a variant of the SA Driver.Each node comprising the SA can communicate with other nodes comprisingthe SA. However, a node can have both the SA and separate SA driverthereon. Each node must also include a suitable communication protocolor communication protocol driver for the respective network type towhich it is coupled. An exemplary protocol is the WIDE network protocol1062 discussed previously herein, a proprietary appliance networkprotocol utilized by Whirlpool Corporation. For a client not having WIDEnetwork protocol that needs to communicate WIDE messages (e.g., externalclient 1004), a WIDE driver 1064 can be used. A port driver 1072 couplesthe external client 1004 to the network 1050.

Each node can also comprise an arbitrary software component 1060. Thecouplers 1040, 1042, for example, may not. The SA driver 1016 is asoftware element configured to allow an arbitrary software component tocommunicate with the SA 1018 over at least one network. An arbitrarysoftware component is any software component or subcomponent thatperforms a useful function. Examples include, but are not limited to, acommunication driver, an application, a user interface, a controlalgorithm, message routing, a control for an operational cycle, messagehandling, data storage, data transformation, data referencing, andsoftware that instructs other software. The SA driver 1016 can receiveand at least partially interpret messages from the SA and/or fromanother SA driver, which are specified as feedback events. In someinstances, the SA driver 1016 can also send command messages to the SA1018. In this respect, the external clients 1002, 1004 can have fullcapability act as an accessory to communicate with and to enhance oralter the operation of the appliance.

It will be understood that any or all of the external clients 1002,1004, the couplers 1040, 1042, and the internal clients 1010, 1012 canbe physical devices that have a processor, a memory, software,circuitry, and some source of power. In the general sense, they arecoupled to transmission media and are preferably configured to takeinformation from the memory and with the processor and the circuitry,produce a signal representing that information in the transmissionmedia. When the information includes an identifier in memory, the nodeor client is discoverable by other nodes connected via the transmissionmedia.

The consumable holder 16 can contain all the functionality andcomponents of a smart coupler 1040, 1042 and participate in all theembodiments of a smart coupler in communication with an appliance 1000,12. Therefore in one embodiment, a consumable holder 16 is a smartcoupler which further physically contains a consumable 24 and that canalso be enabled to directly actuate the introduction of a consumable 24into an appliance. Similarly, the consumable holder 16 can be a client(internal as at 1010, external as at 1002, or remote on a differentnetwork as at 1004) and communicate with an appliance 1000, 12, 1006,either directly or via a smart coupler 1042, 1040.

Likewise, the consumable reader 22 can contain all the functionality andcomponents of a smart coupler 1040, 1042 and participate in all theembodiments of a smart coupler in communication with an appliance 1000,12, 1006. Therefore in one embodiment, a consumable reader 22 is a smartcoupler which further retrieves information about a consumable 24 andcommunicates that information to an appliance. Similarly, the consumablereader 22 can be a client (internal as at 1010, external as at 1002, orremote on a different network as at 1004) and communicate with anappliance 1000, 12, 1006, either directly or via a smart coupler 1042,1040.

Discovery

Discovery is a process by which a first node in communication with atleast one coupled network sends discovery messages to the network ornetworks. Discovery messages generally comprise at least some queryinformation specifying what the sender of the discovery message seeks.The information sought can be information such as another node, anappliance, a client, an arbitrary software component, a devicecomprising a node, a coupler, or one or more of a plurality of softwareelements on any node.

A discovery confirmation message is a reply message sent to the senderof a discovery message. Discovery reply messages typically compriseconfirmation information and identification information. Theconfirmation information is an acknowledgment in the form of a positiveor a negative response. The identification information is informationenabling the sender to send subsequent messages to that which has beendiscovered.

Where more than one network is connected by a coupler, such as couplers1040, 1042, a message received by the coupler from one network can bepropagated and sent to the second network. The coupler may create asecond separate message with the same information compatible for asecond network, but together, the first and the second messages areconsidered a single propagated message, even though they may beliterally two messages. A propagated discovery message, then, is adiscovery message that is propagated to a receiver. A coupler may beconfigured to inspect propagated messages to prevent propagation of acircular message, i.e., a sent message that is also unknowingly receivedby the sender on a second network to which the sender is coupled. Atleast the coupler 1040 may have a routing table including proxyidentifiers of the functionalities of the second node. As well, thecoupler 1042 may have a routing table including proxy identifiers. Adiscovery message sent by the node 1020 is received by the coupler 1042,which evaluates the message in accord with the routing table andpropagates the message to the next node, coupler 1040. Similarly, thecoupler 1040, evaluates the propagated message in light of the routingtable, and propagates the message to the next node in line, which may bethe second node.

See, for example, FIG. 9 illustrating a system where resources in anappliance can be monitored, managed, or changed. A likely scenario has acoupler 2000 connected to an appliance 2002 similar to appliance 12 by anetwork 2004. The coupler 2000 also connects to a coupler 2006 vianetwork 2008 that may be a different type of network from network 2004.Coupler 2006 connects to a source 2010 of information about resourcesused or generated by the appliance 2002 by a third network 2012 that maybe a different type of network from either network 2004 or network 2008.Assume that the source 2010 wants to send information about the resourceto the appliance 2002. The invention enables a node in the source 2010on network 2012 to communicate with a second node, having SA forexample, which may be among several on the appliance 2002. We assumethat the source 2010 has at least an appropriate communication driver,or one of the couplers has software to translate any message from thesource to the communication protocols of the incorporated WO2006135726,for example.

In this scenario, the source 2010 sends a discovery message over thenetwork 2012 seeking any consumer of resources to which the source wantsto send information. The coupler 2006 receives the discovery message,translates the message, if necessary, and propagates the discoverymessage to the next nodes over the network 2008, including coupler 2000.Coupler 2000 receives the discovery message, translates the message, ifnecessary, and propagates the discovery message to the next nodes overthe network, including the appliance 2002. The relevant nodes in theappliance 2002 evaluate the message and determine a discovery replymessage, and send respective replies. Here, we assume at least one replyis positive.

The discovery reply message is received by the coupler 2000, whichpopulates its routing table and sends it to the coupler 2006, whichpopulates its routing table and sends it to the source 2010 in accordwith the foregoing process. Each node retains the relevant identifiersso that subsequent message can be communicated without repeating thediscovery sequence. As well, those nodes with memory, such as thecouplers, can be configured to save messages.

With this structure, a source of information about a resource such aselectricity, hot water, gray water, gas, water, replaceable parts, orother consumables, can request a change in the operation of theappliance based on the information. For example, if an electric utilityis facing a brownout, a source of information about the electricity canrequest that an electric dryer not commence an operation for a period oftime. Similarly, a source of consumables, such as filters or spareparts, can ascertain from an appliance the status of the consumable andsend information about the timing and availability of replacement.

Likewise, the consumable holder 16 can effect the cycle of operation ofthe appliance connected thereto in response to information from a sourceof consumables or to information from a source of information about aresource. The consumable holder 16 can also initiate, respond to, and/orpropagate discovery messages. Further, the consumable holder 16 cancreate and or comprise network routing information.

FIG. 10 illustrates the transfer of an operation cycle accessory betweentwo appliances, Appliance 1 and Appliance 2. A removably coupledoperational cycle accessory 3 has, as part of its data portion, datawhich is associated with an identifier of a particular appliance. Inthis way, when the cycle engine 73 in either Appliance 1 or 2 seeksdata, it can include in its request an identifier that will determinethe correspondence of the data retrieved from the data portion table forthe identifier. With this capability, the operational cycle accessory 3can be removably coupled with more than one appliance and is operablewith as many appliances at the data portion table has identificationsupport for.

Likewise, when an arbitrary software component configures the cycleengine 73 through communications, the arbitrary software component canfirst interrogate, through useful communications, the appliance toascertain its identification whereby that identification is used withthe data portion table to retrieve the appropriate data about the cyclestructure to be built. The arbitrary software component can then sendmessages to the API of the cycle engine 73 to build the appropriatecycle structure 71 for the appliance.

Consumable Reader as a Smart Coupler

Looking now at FIG. 11, a consumable reader 300 is configured to obtaininformation associated with consumables 304. One or more consumables 304may be contained in one or more consumable holders 314 similar to theaforementioned consumable holder 16. The consumable reader 300 can be aform of a smart coupler as in FIGS. 8 and 9. In such case, one purposeof the consumable reader 300 comprises obtaining information associatedwith consumables 304 and communicating all or a portion of thatinformation to at least one functional component 310 of an appliance 312resulting in an effect to a cycle of operation in the appliance 312 orin the consumable holder 314. As discussed previously, the consumable 24can be an article. In one embodiment, the appliance 312 comprises atleast one instance of a cycle architecture 69 and an optional cycleoperations accessory or functional component 310. Typically, anappliance 312 similar to appliance 12 comprises the functional component310. The information associated with consumables 304 obtained by theconsumable reader 300 can thus include not only data about a consumable304A, but also a cycle structure 304B, data for a response to a querymessage from a functional component 304C, and indirect representationsof a cycle structure 304D. Any or all of the data can optionally be inthe form of at least one well formed message according to a packetstructure or a portion thereof. One example of a packet structure is theSA packet structure disclosed in the incorporated WO2006135726. Asmentioned earlier, data about a cycle structure 304D can include directcommands to the functional component 310 or parameters about operatingcycles, including user preferences or environmental parameters.

More examples of information associated with consumables 304 include thequantity of consumable pieces, quantity by volume or by weight, date ofmanufacture, manufacturer, data about its transit from manufacture,distributor, market, and consumer, data about the temperature duringtransit, nutritional information like calories, fat grams, percent dailyallowance of essential vitamins and minerals, a list of medicalconditions under which a consumable should not be consumed, data aboutthe relationship between the consumable and known diets, known medicalconditions, and known reactions to known medications, and the like. Theinformation associated with consumables 304 can further includeappliance or component identifier data in accord with the messagingprotocol of the software architecture. Yet further, informationassociated with consumables 304 can include condition of the consumable,initial conditions for the consumable, data relating to a fill processfor the consumable holder, an attribute of the consumable, an attributeof a sensor, an attribute of the consumable holder, a notificationtrigger rule associated with the consumable, historical informationabout the consumable, usage instruction relating to the consumable,dietary and allergenic information relating to the consumable,purchasing information, advertising information, recipe information,supply chain information, ingredient information, usage informationrelating to the consumable, country of origin for at least one of aplurality of ingredients in a consumable, energy consumption attributedto the making and delivering, information relating to carbon emissionsin the making and delivering, information relating to the un-naturalagents used in the making and delivering, information relating to theenvironmentally friendly agents used in the making and delivering,information about the treatment of animals in the making and delivering,information relating to the working conditions used in the making anddelivering, and information relating to the toxic agents used in themaking and delivering. Information about un-natural agents associatedwith a consumable can include such things as data about pesticides,steroids, and fertilizers associated with the manufacture, delivery orcomposition of the consumable.

As mentioned earlier, information associated with consumables 304 willbe in a consumable information holder 306 that will typically be amemory location somewhere. That memory location can be in the consumableholder 314, or on a surface on a consumable holder 314, which can be oneof a bag, a box, a carton, a bottle, a can, a bowl, a dish, a plate, orany other rigid or semi-rigid body suitable to contain a substance.Information can be stored on a removably coupled article comprisingmemory attached to the surface of the consumable holder 314, such as aperformance tag 320. Information can also reside on a consumable 316itself if the consumable were enabled to store retrievable informationas by etching, embossing, or imprinting. An example of a consumable 316enabled to store retrievable information would be food with informationdirectly printed on or etched into the food using edible ink. Anotheroption is a consumable data pod 318, which is an article comprisingmemory enabled to store retrievable information about a consumable. Anexample of a consumable data pod is an article containing data about aconsumable potentially further comprising consumable meta data.Consumable meta data can be such data as quantity of consumable pieces,quantity by volume or by weight, date of manufacture, manufacturer, dataabout its transit from manufacture, distributor, market, and consumer,data about the temperature during transit, nutritional information likecalories, fat grams, % daily allowance of essential vitamins andminerals, a list of medical conditions under which a consumable shouldnot be consumed, data about the relationship between the consumable metadata and known diets, known medical conditions, and known reactions toknown medications, and the like. The consumable data pod 318 ispreferably consumed by the appliance cycle of operation that alsooperates on the consumable without degradation to the consumable or tothe overall objective of the process operating on the consumable.Information can also reside on a performance tag 320 attached or affixedto an article, as in the case of an RFID tag applied to a laundryarticle.

As well, information can be stored in any other memory location 322,such as memory within a node in the appliance 312 or within theconsumable reader 300 itself. The information associated withconsumables 304 can be stored in removably coupled memory within theconsumable reader 300. It should be understood that, in all cases,information associated with consumables 304 can further includeappliance identifier data enabling the functional component to receivethe most appropriate data about a consumable according to the connectedappliance 312.

In one embodiment, the functional component 310 detects the coupling ofthe consumable reader 300, queries the consumable reader for informationassociated with consumables 304, and a cycle structure 71′ (see FIG. 5)is created according to the data about the consumable.

In another embodiment, the consumable reader 300 is given or infers a‘start command’ in which it selectively retrieves data about anoperating cycle, changes the mode of a software operating layer of theappliance, and commands an alternate software layer of the applianceaccording to the data about an operating cycle. The consumable reader300 can then retrieve data about an operating cycle, establishcommunication with the functional component 310, and create a cyclestructure. In one variation, the cycle structure is created in thememory of the consumable reader 300 and the consumable reader uses thetechnique of the first embodiment to perform the cycle of operation.

The consumable reader 300 can further comprise an arbitrary softwarecomponent 324 of the functional component which creates the cyclestructure by communication with the API of the cycle engine, preferablyusing an embedded virtual router and discovery messages to establish areference to the cycle engine's API. See FIG. 5.

In certain embodiments, at least one cycle structure is present in thememory of the consumable reader 300, and at least one cycle structure ispresent in the memory of at least one appliance functional component310. The cycle structures can be functionally aggregated such that thecycle architecture is disposed to selectively operate in response toeither cycle data structure. In this case, a user interface can be usedto aggregate information about an appliance operating cycle from morethan one component for display, modification, or selection by a user.

The functional component 310 can selectively detect the coupling of theconsumable reader 300 to an appliance 312, and the consumable reader isgiven or infers a ‘start command’. Upon the selected event, the cycle ofoperation of the appliance 312 can obtain and communicate with theinformation associated with consumables 304. This direct communicationwith the information associated with consumables 304 is facilitated bythe consumable reader 300 acting as a smart coupler. Alternatively,direct communication is facilitated by memory within a node incommunication with an executing operation cycle previously populated bythe consumable reader that is acting as a smart coupler.

The consumable holder 16, 314 can include or can be coupled to aconsumable reader 22, 36, 300. When a consumable holder furthercomprises a controller such as controller 32 (see FIG. 2) in operablecommunication with a network, the consumable holder 16 is a smartcoupler in that it is the mechanism to transfer data from the consumableinformation holder 306 to a node on the network. The consumable holder16 can also be a consumable reader 300 in that from the perspective of afirst node of the network, the consumable holder 16 is the node on thenetwork that supplies the functionality of the consumable reader 300.Therefore in one embodiment, a consumable holder is at least one of asmart coupler and a consumable reader that further physically contains aconsumable and can also be enabled to directly actuate the introductionof a consumable into an appliance.

Message Binding

Further explanation of message binding may be helpful with respect tothe incorporated disclosure of WO2006135726 and the messaging of a fullyenabled consumable holder according to the invention. The softwarearchitecture can preferably support and promote both asynchronous andsynchronous data collection. Asynchronous memory polling, for example,is available in the Core API (API ID=1). There are at least twoavailable embodiments of synchronous data collection.

Understanding the invention related to synchronous data collection ishelped by an understanding of the concept of bounded updates. Boundedupdates are events that are grouped together as a snapshot of theappliance state taken during the same scan of the host microprocessor'smain loop execution. The appliance control main loop will allow for aniterative update of feedback variables that are registered with anappliance eventing engine. Each registered variable is monitored andonly those that change value according to their memory monitor changeoperator are broadcast as updates to the client. When updates are in theprocess of being broadcast, no new updates are allowed in order topreserve the snapshot in time.

In the first embodiment, a snapshot is communicated to the client usingthe MMP flag in Byte 2 of the software architecture header as shown inthe application protocol as shown in FIG. 4 of WO2006135726. While theMMP is true, more messages are pending for the snapshot. When MMP isfalse, the current message is the last message in the snapshot.Therefore, if the first message of a snapshot is the only message inthat snapshot, MMP will be false.

The example in FIG. 9 of WO2006135726 illustrates a bounded command(Cycle+Temperature+MMP) with acknowledgements, followed by twoconsecutive bounded updates. Where bounded refers to elements ofprotocol which indicate to the receiver that more messages are comingfrom the source and that data processing by the application logic of thereceiving component should be delayed until the bounding indicators ofthe protocol within the packet structure (MMP bit 7) indicate a completetransaction at which time data processing by the application logic ispermitted. Notice that updates do not begin until bounded commandexecution is complete, providing the client the ability to filter awaytransient feedback data. Bounded commands are provided by the samemechanism, MMP, as bounded updates in order to provide applications agreater level of control.

The example of FIG. 9 in WO2006135726 is conceptual. The actualmechanism is MMP. However for illustrative purpose, the bounded commandbegins with an initial “begin” command initiator (MMP set) and includescommands to set a washer cycle to wash, a recipe status to ready, awater temperature to medium, again a recipe status to ready, and finallya cycle start indicator, followed by a command terminator (MMP unset).It can be noted that, in FIG. 9 in WO2006135726, updates, such as byeventing, are disabled to prevent updates from happening before thebounded command is complete. In addition, a “process command” indicatoris shown periodically throughout the bounded command processing in theappliance to illustrate the portions of the command issued from theclient 16 through the internal communications network are processed.

In the bounded updates, the updates are once again enabled since theywere disabled at the beginning of the bounded command to allow theappliance to report its status to the client. In the example shown inbounded updates, the acknowledgment state is shown to ready, the cycleis reported as wash, the state is reported as running, the basket isreported as fill, the pump is reported as on, and the temperature isreported as medium. Again, beginning and terminating indicators enclosethe bounded update 44. These beginning and terminating indicators can bereported by use of the flag, MMP, in the application packet structure asdiscussed in FIG. 4 of WO2006135726 or another method which would beapparent to one skilled in the art of network protocol.

In the bounded update, the basket is reported as agitate, the pump isreported as off and the motor is reported as on. Again, beginning andterminating indicators (MMP) enclose the bounded update 46. Without thebeginning and terminating indicators (MMP), the client cannot deduce arelationship between the updates from the appliance. However, withbeginning and terminating indicators (MMP), the client can deduce arelationship between the events.

The second embodiment of synchronous data collection is shown in FIG. 32of WO2006135726. Generally, a node comprises at least a micro-processor,a memory, software, and circuitry coupled to a transmission media wherethe node is configured to take information from the memory of themicro-processor and, with the circuitry, produce a signal representingthat information onto a transmission media. Two nodes in communicationwith each other could be two micro-processors on a single printedcircuit board connected by a serial communications or two computersconnected via the internet.

As shown in FIG. 12, it is conventional for a command source 220 to senda complete command within one complete message to a command executor222. The invention, however, contemplates using multiple messages toconvey the elements of a command so that a command can be modular andcan be composed by command elements. For this to work, the commandexecutor 222 needs to know when to execute the command comprised ofmultiple command elements, each of which were sent as an independentsingle command message. The invention provides a solution by providing abegin command group message 224 and an end command group message 226,which inform the command executor 222 as to the which command elementsbelong together for the purpose of executing a plurality of commandelements as a single aggregated command.

FIG. 12 shows how the command source 220, using a begin command groupmessage 224 and an end command group message 226 bounding a series ifindependent command messages 228 can create a command group 230. Withouta begin command group message 224 and an end command group message 226,the command executor 222 cannot deduce a relationship between commandmessage 1, 2, through N. However, with the begin command group message224 and the end command group message 226, the command executor 222 candeduce a relationship between the command messages 228. In messageaggregation, whether data collection or batched commands, the MMP flagcan be used to identify the beginning and ending of the message group.

A consumable holder communicating with an appliance on a network using anetwork protocol which supports message binding can be an importantfeature relating to the consumable holder's controller 32 in the processof executing logic which might result in one of the actuation of theintroduction of a consumable to an appliance and an effect to anappliance cycle of operation or display of a user interface. This isbecause the execution logic may use a plurality of data received in aplurality of messages wherein the plurality of data functionally belongsto a plurality of valid data sets. With message binding, the executionlogic will use a single valid data set per execution scan wherein thevalid data set are constructed from data received in the plurality ofmessages according to groupings implied by the binding.

This technique can also be used to batch event, as shown in FIG. 13,which shows an eventing software architecture for communications betweenone node, event source 200, and a second node, event observer 202. Thesoftware architecture contemplates the event source sending a message tothe event observer about the event. Rather than sending a singlemessage, however, the event source 200 can use a begin event groupmessage 204 and an end event group message 206 to create an event group208 from a series of individual event messages 210. An advantage ofsending separate messages in this technique is that it more efficientlyuses the messaging architecture in rapidly changing states of anappliance and minimizes the number of uniquely identified messagesneeded to express the state of an appliance. Without the begin and endevent group messages, the event observer 202 cannot deduce arelationship between any event messages 1, 2, . . . , and n. However,with the begin and end event group messages, the event observer 202 candeduce a relationship between the events.

EXAMPLES Messaging

Implementation of the inventive concepts in a washing machine can beseen in FIGS. 14-16. It is assumed that the washing machine is able todiscover or detect the presence of the consumable holder and itsfunctionalities. Likewise, the consumable holder is able to detect thepresence of the washing machine control. Each is able to discover thecapabilities of the other (through the use of standard interfaces) anduse this information to collaborate together to provide new features forthe user.

A first mode in FIG. 14 shows the messaging that might be employed whendispensing is needed during a cycle. The appliance control commands theconsumable holder to dispense in a specific manner using a set ofstandard commands for dispensing. An example would be “dispensedetergent, medium size.”

FIG. 15 illustrates a second scenario where the appliance control cancommand the consumable holder to dispense at the appropriate time in thecycle through a set of standard commands. In addition to these commands,the consumable holder can gather other information from the appliancecontrol and its related sensors such as but not limited to load size,load type, soil level, and temperature. The consumable holder can usethis status information along with its own dispensing algorithm todispense a more effective or more accurate chemistry amount and/or type.In addition to gathering cycle or sensor-based data from the appliancecontrol, data can also be gathered from the user interface. This couldinclude details such as detergent concentration, or the type of cycleand options selected by the user. This information can also be used toimprove the performance of the dispensing algorithm. Finally, if theconsumable holder is able to sense properties about the consumable thatit is holding, such as the brand or type of chemistry, this informationcan also be integrated with the dispensing algorithm to improveperformance.

FIG. 16 illustrates a scenario where the consumable holder can usestatus information from the appliance control to make decisions on whento dispense or even to change the cycle behavior by commanding theappliance control to execute certain processes. An example of this couldbe inserting a catalyst-type action into a cycle when dispensing certainchemistries by commanding the appliance control to spin and dispensesimultaneously. Another example could be commanding the washer to heatthe water to a specific temperature in combination with dispensing inorder to best activate a chemical reaction upon dispensing a particularchemistry. The consumable holder can also provide status information tothe user interface during this operation to notify the user about theimprovement it is making to the appliance cycle process.

Smart Filtration

Another example of a consumable holder according to the invention isfound in filtration in a refrigerator as shown in FIGS. 17-20. FIG. 17illustrates a water filter cartridge system 5030 that may findparticular utility in a water dispensing system 5032, such as found in arefrigeration appliance 5034. The present invention also has utility inother appliances and environments and for filtering liquids other thanwater. For purposes of disclosing an embodiment of the invention, itwill be disclosed in the environment of a water dispensing system 5032in a domestic refrigerator appliance 5034 where the water is dispensedat a door 5036 of the refrigerator. The refrigerator can include a userinterface (not shown) as for purposes discussed above. The water issupplied via a water line 5038 plumbed into a building supply, andpasses through a cabinet 5040 of the appliance 5034, and into therefrigerator door 5036 at a hinge 5042 for the door. The water line 5038in the door 5036 is connected to the water filter cartridge system 5030,from which a connecting water line 5044 leads to a water dispenser 5046accessible from outside of the door 5036. The water filter cartridgesystem 5030 may be accessible for removal and replacement, such as atstationary ventilation grill 5048 positioned below the door 5036.

As illustrated in more detail in FIGS. 18-19, the water filter cartridgesystem 5030 comprises a filter cartridge 5050 and a cartridge housing5056 which may be permanently attached to the refrigerator 5034, such asvia a mounting bracket 5057. The housing 5056 may be in the form of acylinder with a first open end 5058, and a second end 5060.

The filter cartridge 5050 can have a structure similar to that of aconventional filter cartridge including a porous filter body (not shown)that may have a cylindrical shape, with a similarly shaped impermeablehousing 5062 having integrally formed end caps. Alternatively, the endcaps can be formed separately and removably attached to the housing 5062by any suitable means, such as by a snap fit. The cartridge 5050 has anouter diameter sized to fit within the housing 5062. One end of thehousing comprises inlet and outlet passages (not shown) to allowunfiltered and filtered liquid, respectively, to flow therethrough.

The filter cartridge 5050 further comprises an identifying element 5075.The identifying element 5075 can be any device capable of storing orproviding data and/or information associated with the water filtercartridge system 5030 such as, but not limited to, a barcode, a magneticstrip, a microprocessor, a memory chip, a license key, a specializedstructure, a smart card, matermetrics (magnetic nanotechnologyfingerprints), a magnetic switch, or an RFID. As shown, the identifyingelement 5075 comprises a memory chip. The identifying element 5075 canstore a unique identifier for a particular filter cartridge, as well ascharacteristics and other information associated with the filtercartridge and/or its use.

Alternatively, the identifying element 5075 can be separate from thefilter cartridge 5050, such as in the form of a license key (not shown).The license key would be configured to plug into a connector on theappliance 5034 and to communicate with the appliance 5034 and across thenetwork of the appliance 5034. The license key can contain a uniqueidentifier, as well as information about the filter cartridge 5050.

The appliance 5034 can comprise a reading element 5076, which can be atype of consumable reader, for communicatively coupling the appliance5034 with the identifying element 5075. In the embodiment illustrated inFIGS. 18-19, the reading element 5076 is positioned on the cartridgehousing 5056 and is communicatively coupled to the appliance 5034 viawires 5074 attached to an appliance contact 5072. The reading element5076 extends through the cartridge housing 5056 such that the readingelement 5076 is configured for placement against or adjacent to theidentifying element 5075 when the filter cartridge 5050 is inserted intothe cartridge housing 5056. If necessary, the appliance 5034 and/or thecartridge housing 5056 can include positioning elements (not shown) forensuring proper alignment between the identifying element 5075 andreading element 5076 when the water filter cartridge 5050 is insertedinto the cartridge housing 5056, as is shown in FIG. 19.

The appliance contact 5072 is configured to communicatively couple tothe appliance 5034 when the cartridge housing 5056 is mounted in theappliance 5034. This can be accomplished by configuring the housing 5056and/or mounting bracket 5057 to maintain the appliance contact 5072 in aposition adjacent or abutting a housing contact (not shown) in theappliance 5034. The housing contact can be communicatively coupled to anetwork of the appliance 5034.

In other embodiments, the reading element 5076 can be positioned on theappliance 5034 or elsewhere on the cartridge housing 5056. For example,the reading element 5076 can be installed near the cartridge housing5056 in a machine compartment of the appliance 5034. Installing thereading element 5076 in the appliance 5034 is particularly useful in theevent that the identifying element 5075 does not require a wiredconnection with the reading element 5076 in order to communicate, suchas when the identifying element 5075 is an RFID chip and the readingelement 5076 is an RFID reader.

The reading element 5076 is configured to obtain, exchange, store,deliver, detect, and/or verify data and/or information by communicatingwith the identifying element 5075. The reading element 5076 can readdata from the identifying element 5075, read and write data from/to theidentifying element 5075, or engage in a two-way exchange of data withthe identifying element 5075.

The reading element 5076 is communicatively coupled with a controller(not shown) of the water filter cartridge system 5030 such that thereading element 5076 can send data obtained from the identifying element5075 to the controller. The controller can comprise a control boardhaving software architecture configured for communication on the networksuch that the controller can communicate with other control boards orclients on the network. The controller can further comprise a uniqueidentifier identifying at least one functionality associated with thefilter cartridge system 5030 that can be communicated to the appliance5034. The reading element 5076 can be configured for one or two-waycommunication with the controller. The controller can be amicroprocessor having an internal memory or a memory associatedtherewith. The controller can be part of the reading element 5076.Alternatively, the controller can be located at any another point on thenetwork of the appliance 5034 or on a network connected to the appliance5034 and enabled for communication therewith. The controller can beconfigured for one or two way communication with the appliance 5034 andcan be communicatively coupled to the appliance 5034 in a wired orwireless manner.

The Filter Cartridge System as a Node on a Network

The filter cartridge system 5030 can be a node on the network of theappliance 5034. As part of a node, the controller can communicateinformation related to filter cartridge 5050 (a consumable) to theappliance 5034. The controller can inform the appliance of theproperties of the filter cartridge 5050 and the correct usageinformation using information received from the reading element 5076.The controller can be coupled to the network of the appliance 5034 via adirect wired connection or by a wireless connection. The controllerincludes the software architecture that enables communication andconnection to the network of the appliance 5034. The controller canmonitor and record events, communicate with other nodes on the networkof the appliance 5034, or affect a cycle of operation of the appliance5034. The controller can propagate and transfer information toadditional networks, such as a third network connected to the network ofthe appliance 5034, or any other networks connected thereto.

The filter cartridge system 5030 can be discovered by other nodes on thenetwork of the appliance 5034 using discovery messages. By takingadvantage of this feature and sending messages to and from thecontroller, the appliance 5034 can automatically detect the water filtercartridge system 5030 and discover its capabilities. This also enablesthe water filter cartridge system 5030 control methods and algorithms toreside on the controller, rather than on the main appliance control.Because of this modular functionality, the appliance 5034 will be ableto accept a larger variety of filters and can easily adapt to newfeatures and configurations associated with the filter cartridge system5030. The appliance 5034 can also automatically discover filtercartridges 5050 and the status of any installed filter cartridge 5050can be communicated to the appliance 5034. Similarly, the filtercartridge system 5030 controller can query the network for the uniqueidentifiers of the functionalities available in the appliance 5034.

Using the software architecture, the water filter cartridge system 5030can be used to provide instructions or directions for changing appliance5034 behavior. The controller of the filter cartridge system 5030 cansend messages to the appliance 5034 to configure the appliance 5034. Thefilter cartridge 5050 can include data and information on theidentifying element 5075 that can provide characteristics or informationto the appliance 5034 through the reading element 5076. This informationwill be used by the appliance 5034 to modify appliance operation. Theidentifying element 5075 contain at least one of additional cycles ofoperation, updated cycles of operation, historical information relatingto cycles of operation experienced by the appliance, and software toreconfigure the software architecture of the filter cartridge system5030 or the appliance 5034.

For example, the filter cartridge 5050 can send the appliance 5034information regarding volume capacity, flow rating, filtrationcapabilities, and time/temperature dependence of the filter cartridge5050. The appliance 5034 can use this information to modify filtercartridge parameters stored in the system, such as by changing a filtercartridge life algorithm. This also enables the use of a number ofdifferent filter cartridges because as long as a desired filtercartridge is configured for insertion into the cartridge housing 5056,the appliance 5034 can discover the characteristics of the filtercartridge in order to learn how to implement it correctly.

Filter Cartridge Usage Sensing

Communication between the identification element 5075 and the readingelement 5076 can be used for notifying a user that the filter cartridge5050 has expired and needs to be replaced. This can be accomplished byactivating at least one filter status indicator (not shown) when thefilter requires replacement. The filter status indicator can be an LED,a sound, and/or a display on a user interface, such as a message orimage. The filter status indicator is activated when informationobtained by the reading element 5076 indicates that the filter cartridge5050 needs to be changed. Upon replacement of the filter, the indicatorwill automatically be turned off and reset.

Another example of an indicator that can be used to draw a user'sattention to the filter cartridge 5050 and that can also providefeedback regarding the status of the filter cartridge 5050 is anindicator cap. The indicator cap is best used when the filter cartridgesystem 5030 is easily visible to a user. In the preferred embodiment,the indicator cap comprises two types of plastic. One type of plastic istransparent, and the type of plastic is opaque. The transparent plasticfunctions as a light pipe and can be molded to include indiciaassociated with the filter cartridge 5050. The indicator cap can furthercomprise an LED light positioned between the layers of plastic toilluminate the indicia. The LED light can be changed to different colorsor blinked on and off to provide information about the status of thefilter cartridge 5050. For example, when a new filter cartridge 5050 isinstalled, the LED light can be a steady blue color. When the filtercartridge 5050 has only 10% remaining capacity, the LED light can be asteady red color. When the filter cartridge 5050 expires, the light canblink red on and off until the filter cartridge 5050 is replaced.

The controller can store the unique identifier associated with eachfilter cartridge 5050 installed in the cartridge housing 5056. When afilter cartridge 5050 is installed in the cartridge housing 5056, thereading element 5076 can obtain data from the identifying element 5075regarding the filter cartridge 5050. The controller can use this data tocheck the unique identifier of the filter cartridge 5050 againstpreviously stored unique identifiers associated with previouslyinstalled filter cartridges. If the controller determines that theunique identifier already exists in the memory, the controller caninstruct the reading element 5076 to retrieve information from theidentifying element 5075 regarding whether the filter cartridge 5050 haswas any remaining capacity. If the control determines that the filtercartridge 5050 has capacity, the controller can enable operation of thewater dispensing system 5032 and can update filter-related parameters inthe memory. If the controller determines that the filter cartridge hasno remaining life, the user can be alerted that a filter replacement isrequired. If a filter cartridge 5050 is installed and has a uniqueidentifier not stored in the memory, the controller can record theunique identifier and reset any filter status indicators and storefilter-related parameters in the memory.

The identifying element 5075 can include information such as the type,brand, serial number, and flow rate of the particular filter cartridge5050. Because the reading element 5076 and controller can read and storethe unique identifier associated with each filter cartridge 5050, thecontroller is able to distinguish a new filter cartridge from a usedone. The controller can also store dates and times of filter cartridgeusage in the memory for service and warranty information purposes.

The identifying element 5075 and/or controller can track the totalvolume of water that passes through each filter cartridge 5050 and/orthe total time that each filter cartridge 5050 is used and associatethat information with each filter cartridge's unique identifier. Thisfunction can be used to monitor water quality and to help maintainproper filtering characteristics and energy requirements.

The filter cartridge 5050 can also include various sensors fordetermining parameters associated with filter cartridge usage, such as awater contaminant sensor, a water conductivity sensor, a turbiditysensor, electrochemical sensors, and leak sensors. These sensors cancomprise but are not limited to simple electrical leads or contacts, IRsensors, ultrasonic sensors, temperature sensors, and/or capacitivesensors. Information gathered by the sensors can be sent to thecontroller and can be used to control filter cartridge 5050 and filtercartridge system 5030 operation. Based on the sensed parameters andinformation about the filter cartridge 5050 obtained from theidentifying element 5075, the performance of the filter cartridge 5050can be adjusted. For example, using the user interface, the user selectoperational properties of the filter cartridge 5050 and filter cartridgesystem 5030 that will lengthen the life of the filter cartridge 5050while diminishing the level of filtration of water, or vice versa.

The leak sensor can be positioned such that any water leaking from thefilter cartridge 5050 or cartridge housing 5056 will contact the sensor.The sensor can then notify the controller of the leak, and thecontroller can shut off a water supply or halt operation of theappliance 5034, dispensing system 5032, or filter cartridge system 5030.

In the event that a particular filter cartridge 5050 can be used to addcertain additives to the water, such as vitamins and minerals orflavorings, the controller can be used to adjust additive dosing basedon information received from the sensors, from the identifying element5075, and from a user interface. If the filter cartridge 5050 isdispensing vitamins and/or minerals, the controller can use the sensorsand information from the identifying element 5075 to ensure that thelevel of vitamins and minerals being dispensed is within a range deemedsafe for consumption. The user interface can also be updated to reflectthe particular additives available for dispensing, and the user cancontrol the type and dosing of any additives being dispensed.

Compatible Filter Detection

The identifying element 5075 can enable automatic detection of acompatible filter cartridge 5050. Upon insertion of a cartridge 5050into the housing 5056, the reading element 5076 can detect the presenceof the identifying element 5075 and interact with the identifyingelement 5075 to ascertain whether the filter cartridge 5050 iscompatible with the filter cartridge system 5030 and appliance 5034. Adetermination of filter cartridge compatibility can be made based on oneor more desired filter cartridge traits, such as filter cartridgemanufacturer, filter cartridge size, filter type, remaining filtercapacity, filter age, and/or whether the filter cartridge is new orused. This can be accomplished by the reading element 5076, whichobtains filter cartridge information from the identifying element 5075.The reading element 5076 can send the filter cartridge information tothe controller. The controller can compare the filter cartridgeinformation obtained by the reading element 5076 to compatible filtercartridge information contained in the memory of the controller in orderto determine whether the filter cartridge 5050 is compatible.

Alternatively or in addition, the cartridge housing 5056 can include alockout mechanism configured to accept only compatible filter cartridges5050. The cartridge housing 5056 and/or cartridge 5050 can also includeelements (not shown) designed to break or otherwise deform to ensurethat only compatible filter cartridges 5050 can be inserted into thecartridge housing 5056. In addition, such elements can be used toprevent cartridges 5050 from being removed and then reinserted into thesame or into a different cartridge housing 5056.

If a user inserts an incompatible filter cartridge 5050, the user can benotified using a user interface of the appliance 5034, lights, sounds,or any combination thereof. Operation of the water dispensing system5032 can be halted until a compatible filter cartridge 5050 is insertedinto the cartridge housing 5056. Alternatively, the water dispensingsystem 5032 can be configured to bypass the water filter cartridgesystem 5030 in the event that an incompatible filter cartridge isinstalled by a user.

Alternatively, the filter cartridge 5050 and cartridge housing 5056 caninclude an auto-eject mechanism (not shown) capability that wouldmechanically eject incompatible filter cartridges 5050. The auto-ejectmechanism can comprise a motorized latch release or an electromagneticsolenoid that will push the filter cartridge 5050 out of the cartridgehousing 5056 if the filter cartridge is determined to be incompatible.

The filter cartridge 5050 can further comprise a proximity targetlocated thereon, a proximity sensor located on the cartridge housing5056, and a sensor-actuated connector (not shown) located on or near thecartridge housing 5056. The proximity target and proximity sensor can bethe identifying element 5075 and the reading element 5076, respectively.When the filter cartridge 5050 is installed in the cartridge housing5056, the proximity sensor can detect the proximity target on the filtercartridge 5050 and then actuate the connector to close an electricalcircuit. This circuit provides power to one of: an electronic controlthat manages the water dispensing system 5032, an electronic solenoidvalve that turns a water supply on and off, or another electronic devicerelated to the appliance 5034 and the water filter cartridge system5030. In another embodiment, the connector can close the electricalcircuit once the controller or appliance 5034 receives information fromthe identifying element 5075 communicating operational information aboutthe filter cartridge 5050.

Data and information contained on the identifying element 5075 can beencrypted or otherwise protected in order to prevent competitors fromcreating replacement filters without consent.

Filter Cartridge Replacement Process

An exemplary filter cartridge replacement process 5100 is illustrated inFIG. 20. At step 5102, a user removes a used filter cartridge from thecartridge housing 5056. In the event that no filter cartridge 5050 iscurrently in place, the user simply skips step 5102. At step 5104, theuser inserts a new filter cartridge 5104.

If the reading element 5076 is unable to interact or communicate withthe identifying element 5075 at step 5106, an error message is displayed5107 to the user, and operation of the water dispensing system 5032 ishalted, and/or the water filter cartridge system 5030 is bypassed.

If communications between the reading element 5076 and the identifyingelement 5075 are detected, the controller receives communications fromthe reading element 5076 regarding whether the filter cartridge 5050 hasbeen used before. If the filter cartridge 5050 has been used before andhas no further filtration capacity, the error message is displayed 5107,and operation of the water dispensing system 5032 is halted, and/or thewater filter cartridge system 5030 is bypassed.

If the filter cartridge 5050 is new, then filter information isretrieved 5110 from the identifying element 5075 by the reading element5076. The reading element 5076 then sends the filter cartridgeinformation across the network to the controller at step 5112. Once thecontroller receives the filter cartridge information, the controlleranalyses the filter cartridge information at step 5114. Based oninstructions and other information contained in the memory associatedwith the controller, the controller determines whether the filtercartridge 5050 is compatible at step 5116. If the filter cartridge 5050is not compatible, an error message is displayed 5117, and operation ofthe water dispensing system 5032 is halted, or the water filtercartridge system 5030 is bypassed.

If the filter cartridge 5050 is compatible, then at step 5118, thereading element 5076 sends all information obtained from the identifyingelement 5075 to the controller to be stored in the memory, all filtercartridge-related parameters are set, and the user interface, ifpresent, is updated to reflect current filter cartridge 5050information. Normal operation of the water dispensing system 5032 andthe water filter cartridge system 5030 can begin.

The present invention has been described utilizing particularembodiments. As will be evident to those skilled in the art, changes andmodifications may be made to the disclosed embodiments and yet fallwithin the scope of the present invention. For example, variouscomponents could be utilized separately or independently in someembodiments without using all of the other components in the particulardescribed embodiment. The disclosed embodiment is provided only toillustrate aspects of the present invention and not in any way to limitthe scope and coverage of the invention. The scope of the invention istherefore to be limited only by the appended claims.

Creating Cycle Structures

FIG. 21 illustrates how a consumable holder according to the inventioncan facilitate the creation or modification of cycle structures for anappliance, such as the appliance to which the consumable holder might becoupled. A cycle structure can, of course, be created independently of aconsumable holder as by an authoring tool. This may be created, forexample, by a food supplier as illustrated in FIG. 6., or any otherconsumable or article provider of such items as chemicals, detergents,additives, bleaches, softeners, rinse aids, clothing tags and the like.The consumable holder, however, can also facilitate creation ormodification of a cycle structure by accessing information associatedwith the consumable and acting with the cycle engine to create or modifythe cycle structure. The information associated with a consumable willmore than likely be in a consumable information holder (see FIG. 11).The consumable holder can send the cycle structure information gleanedfrom the consumable information holder directly to the cycle engine orreply to a query from the cycle engine. If the information is notdirectly translatable from the consumable information holder, theconsumable holder can execute a conversion to convert the informationassociated with the consumable holder. The converter converts the datato create the cycle structure 71 that the consumable holder cancommunicate to the cycle engine so that it can create the new ormodified cycle structure 71(b).

While the invention has been specifically described in connection withcertain specific embodiments thereof, it is to be understood that thisis by way of illustration and not of limitation, and the scope of theappended claims should be construed as broadly as the prior art willpermit.

1. A consumable holder for use in an appliance configured to perform anoperation cycle related to a consumable in the consumable holder, inresponse to a cycle structure, the consumable holder having or enabledto acquire information about the cycle structure, wherein theinformation about the cycle structure can be communicated to theappliance for use by the appliance to change the cycle structure andthereby change the operation cycle related to the consumable.
 2. Theconsumable holder of claim 1 wherein the information about the cyclestructure is represented by one of key-value pairs, XML, relational datatables, comma separated variable files, a hierarchical composite tree orgraph, byte arrays, data packets, command objects, binary encoded data,data encoded as a programming language such as a C header file, text,scripts, serialized objects, and messages.
 3. The consumable holder ofclaim 1 wherein the consumable holder comprises a sensor and the data isacquired from the sensor.
 4. The consumable holder of any of claim 1wherein at least a portion of the data is acquired from a distinctsource of information about one of the consumable and the consumableholder.
 5. The consumable holder of any of claim 1 wherein theinformation includes data about at least one attribute of the consumablethat would enable the appliance to ascertain the utility of theconsumable.
 6. The consumable holder of any of claim 1 wherein theinformation includes any one of a sound, a graphic, a ring tone, andlicensable information.
 7. The consumable holder of any of claim 1wherein the holder is one of a bag, a box, a carton, a bottle, a can, acartridge, a bowl, a dish, a plate, and any other rigid or semi-rigidbody suitable to contain a substance.
 8. The consumable holder of any ofclaim 1 wherein the data is created by an authoring tool.
 9. Theconsumable holder of claim 8 wherein the authoring tool resides in auser interface operably connected to the appliance.
 10. A performancetag for affixing to one of a consumable holder for use in an applianceconfigured to perform an operation cycle related to a consumable in theconsumable holder and an article adapted to be operated on in anappliance configured to perform an operation cycle related to thearticle, the operation cycle being in response to a cycle structure, theperformance tag comprising one of information about the cycle structureand other information, wherein the one of the information about thecycle structure and other information can be communicated to theappliance for use by the appliance to change the cycle structure andthereby change the operation cycle related to the consumable or to thearticle.
 11. The performance tag of claim 10 wherein the informationabout the cycle structure is represented by one of key-value pairs, XML,relational data tables, comma separated variable files, a hierarchicalcomposite tree or graph, byte arrays, data packets, command objects,binary encoded data, data encoded as a programming language such as a Cheader file, text, scripts, serialized objects, and messages.
 12. Theperformance tag of claim 10 wherein the other information comprises alink to another source of information about the cycle structure.
 13. Anarticle adapted to be operated on in an appliance configured to performan operation cycle related to the article in response to a cyclestructure, the article comprising a performance tag having informationabout the cycle structure, wherein the information about the cyclestructure can be communicated to the appliance by message for use by theappliance to change the cycle structure and thereby change the operationcycle related to the article.
 14. The article of claim 13 wherein theinformation about the cycle structure is represented by one of key-valuepairs, XML, relational data tables, comma separated variable files, ahierarchical composite tree or graph, byte arrays, data packets, commandobjects, binary encoded data, data encoded as a programming languagesuch as a C header file, text, scripts, serialized objects, andmessages.
 15. A consumable holder for use in an appliance configured toperform an operation cycle related to a consumable in the consumableholder in response to a cycle structure, comprising a performance taghaving information about the cycle structure, wherein the informationabout the cycle structure can be communicated to the appliance for useby the appliance to change the cycle structure and thereby change theoperation cycle related to the consumable.
 16. The consumable holder ofclaim 15 wherein the information about the cycle structure isrepresented by one of key-value pairs, XML, relational data tables,comma separated variable files, a hierarchical composite tree or graph,byte arrays, data packets, command objects, binary encoded data, dataencoded as a programming language such as a C header file, text,scripts, serialized objects, and messages.
 17. The consumable holder ofclaim 15 wherein the information includes data about one of appliancetypes, fabric types, and stain types whereby the information can be usedalone or combined with the other information to create or modify a cycleof operation in response to the information.
 18. A consumableinformation holder for use by an appliance configured to perform anoperation cycle related to a consumable in response to a cyclestructure, the consumable information holder comprising informationabout one of the cycle structure and user interface data, wherein theinformation about the one of the cycle structure and user interface datacan be communicated to the appliance for use by the appliance to changethe cycle structure and thereby change the operation cycle related tothe consumable or to render the user interface data.
 19. The consumableinformation holder of claim 18 wherein the information about the cyclestructure is represented by one of key-value pairs, XML, relational datatables, comma separated variable files, a hierarchical composite tree orgraph, byte arrays, data packets, command objects, binary encoded data,data encoded as a programming language such as a C header file, text,scripts, serialized objects, and messages.
 20. The consumableinformation holder of claim 19 wherein the consumable information holderis one of a consumable holder, a performance tag, a consumable, and adata pod.
 21. The consumable information holder of claim 19 wherein theinformation includes data about at least one attribute of the consumablethat would enable the appliance to ascertain the utility of theconsumable.
 22. The consumable information holder of claim 19 whereinthe information includes any one of a sound, a graphic, a ring tone,licensable information, advertising information, usage instructions,purchasing and replenishment information, and ingredient informationrelating to the consumable.
 23. The consumable information holder ofclaim 19 wherein the information comprises two of first and second cyclestructures and first and second user interface data sets.
 24. Theconsumable information holder of claim 23 wherein the first and secondcycle structures and first and second user interface data sets areassociated, respectively, with first and second appliances or appliancetypes.
 25. The consumable information holder of claim 19 wherein theconsumable information holder is configured to receive and storeinformation associated with the consumable